How to resolve (reading 'isServer') error in npm?

Question

Catch this error after npm i. Version npm - 8.0.0, nodejs - 16.11.0.

npm ERR! Cannot read properties of undefined (reading 'isServer')

I guess we need more information. Which packages do you install? Can you provide more error logs? Can you provide the package.json? The error says, that some object is undefined when calling and some function tries to access the "isServer" property of it, which in turn doesn't work... — Der Alex
– Der Alex, Commented Jun 27, 2022 at 6:04

Klaymant · Accepted Answer · 2021-10-24 16:27:18Z

9

I had the same issue with close versions of node and npm. I was using a shared connection from my phone since I wasn't home. When I get back home and used my WiFi things got back to normal.

If you are using such kind of connection then it is probably that causes this issue.

answered Oct 24, 2021 at 16:27

Klaymant

1786 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Miguel Ormita Over a year ago

I highly recommend trying this solution. It worked for me. I was using mobile phone, but switched to pocket wifi(still mobile but not through tethering) and it worked. Prior to this, I tried everything: npm cache verify/clean/--force, delete cache folder manually, installed lower versions on node&npm, cleared temp folder and restarting my machine. And it worked for creating new projects and npm install on existing projects.

TheDeveloo Over a year ago

This seems to be a network problem, I had the same problem but had to use 4G instead of the WiFi

SangyK Over a year ago

It worked for me. Initially, I created a new react project while on my company's VPN. Got the same error mentioned by OP. Tried cache clean, audit fix etc. Nothing worked. Then stumbled upon this thread. I switched back to my personal wifi and the problem was solved.

Dovi Rosner · Accepted Answer · 2022-08-18 01:27:35Z

3

I updated npm and that fixed it! You can update npm like so:

npm install -g npm@latest

If running this command doesn't work then you can try installing npm packages in an Admin Environment.

Hope this helps!

edited Aug 18, 2022 at 1:27

answered May 11, 2022 at 1:58

Dovi Rosner

1232 silver badges8 bronze badges

Comments

Leela Krishna · Accepted Answer · 2022-11-04 13:56:57Z

3

The issue could be due to the network, try to change the network and retry. This solved my issue :)

answered Nov 4, 2022 at 13:56

Leela Krishna

413 bronze badges

2 Comments

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Marcelo Scofano Diniz Over a year ago

Welcome to SO! Although your insight may solve the OP problem, there is an already accepted answer that say it while providing more details than yours.

Tanjin Alam · Accepted Answer · 2022-01-28 05:48:37Z

2

Try to use npm with specific version

for example i was trying to use npm install -g truffle and it did not work

but this one work npm install -g [email protected]

answered Jan 28, 2022 at 5:48

Tanjin Alam

2,6521 gold badge19 silver badges22 bronze badges

Comments

pokz · Accepted Answer · 2021-12-26 15:07:15Z

1

I've got the same issue, then I updated npm to 8.3.0, and the problem is solved.

answered Dec 26, 2021 at 15:07

pokz

111 bronze badge

1 Comment

fudo Over a year ago

May you explain the reason behind that?

FanoFN · Accepted Answer · 2022-01-11 06:21:28Z

1

Copying the npmrc.5 file from: C:\Program Files\nodejs\node_modules\npm\man\man5 to C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm seemed to work for me:

Copy-Item -Path C:\Program Files\nodejs\node_modules\npm\man\man5 -Destination C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm –Passthru

edited Jan 11, 2022 at 6:21

FanoFN

7,1342 gold badges17 silver badges35 bronze badges

answered Jan 8, 2022 at 12:28

bereket girma

111 bronze badge

Comments

nipun-kavishka · Accepted Answer · 2022-01-31 10:23:24Z

1

Try stable Nodejs version 14.16.1 instead of 16. Nodejs 14.16.1 Link

answered Jan 31, 2022 at 10:23

nipun-kavishka

9221 gold badge13 silver badges22 bronze badges

Comments

Tamileniyan · Accepted Answer · 2022-03-13 12:03:22Z

1

Update the latest version of Node.js. Then try to install npm the issue won't come. Check out this URL https://nodejs.org/en/ and install a version recommended for most users.

answered Mar 13, 2022 at 12:03

Tamileniyan

112 bronze badges

Comments

xxfogs · Accepted Answer · 2022-04-18 10:40:48Z

1

I had this same issue, turning off all port forwarding on my router helped.

answered Apr 18, 2022 at 10:40

xxfogs

791 silver badge7 bronze badges

Comments

Md. Sohag Hossain · Accepted Answer · 2022-06-27 05:34:12Z

1

Whenever, I saw this problem. I restarted the computer and it working immediately. I recommend trying this solution.

answered Jun 27, 2022 at 5:34

Md. Sohag Hossain

363 bronze badges

Comments

Zakes Manyoni · Accepted Answer · 2021-10-18 11:32:03Z

0

Based on what I've read on issues related, it seems like there's conflicting global packages and node versions.

Please try uninstalling both node and npm and try again.

Check out these issues for more details:

Node error Cannot read property 'resolve' of undefined

Cannot read property 'resolve' of undefined when using npm to install a package

answered Oct 18, 2021 at 11:32

Zakes Manyoni

3162 silver badges6 bronze badges

Comments

Shamim · Accepted Answer · 2022-01-19 04:04:45Z

0

I had the same issue and tried all the possible solutions. None of them worked. And finally, when I restarted my PC, it worked like a charm :).

answered Jan 19, 2022 at 4:04

Shamim

2362 silver badges7 bronze badges

1 Comment

Eric Aya Over a year ago

Something worked. But it was only active/visible after the reboot. Just rebooting does not fix such errors.

Iván Salazar · Accepted Answer · 2022-01-25 00:40:34Z

0

It happened to me because of the node.js version and an npm update.

Uninstall nodejs
Delete folder C:\Users\Administrator\AppData\Roaming\npm
Install nodejs (v17.x)
In your project folder:

npm install -g [email protected]
npm i --package-lock-only
npm audit fix --force

It worked for me. I hope it helps you :)

edited Jan 25, 2022 at 0:40

answered Jan 24, 2022 at 21:59

Iván Salazar

111 bronze badge

Comments

Francesco Mazzini · Accepted Answer · 2022-12-14 09:23:18Z

0

When I had this problem, I was trying to deploy my NodeJs server in Heroku. The problem was I forgot to load the enviroment variables manually, so it was related to the connection to the DB, that was failing. It happened also locally for the same reason and it was still related to the failing connection to the DB.

answered Dec 14, 2022 at 9:23

Francesco Mazzini

1

Comments

David Williams · Accepted Answer · 2022-02-05 05:04:13Z

-1

I kept running into this problem in different scenarios. I found that because I had used a VPN during my computer session, but not during the time I ran 'npm install', it was throwing this error. I simply reinstalled and restarted and did not enable my VPN during that session. Although, you may not have to completely reinstall-- only restart you PC without using a VPN after restart-- I do not know as I have not tried.

(Specifically I was using Express VPN)

Update: I ran into the problem again immediately after a fresh install and restart. Again I restarted my computer (without a fresh install as I had just reinstalled it.) This seemed to work for the moment. Will update with any permanent fixes I come across.

edited Feb 5, 2022 at 5:04

answered Feb 3, 2022 at 23:37

David Williams

355 bronze badges

2 Comments

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Sebastiano Schwarz Over a year ago

This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. To get notified when this question gets new answers, you can follow this question. Once you have enough reputation, you can also add a bounty to draw more attention to this question. - From Review

Arthigprakash · Accepted Answer · 2023-03-07 11:28:42Z

-2

Change your network and try again ,this worked for me!

answered Mar 7, 2023 at 11:28

Arthigprakash

1

1 Comment

Eric Aya Over a year ago

This is the same solution as in this other answer.

Collectives™ on Stack Overflow

How to resolve (reading 'isServer') error in npm?

16 Answers 16

3 Comments

Comments

2 Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

2 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

16 Answers 16

3 Comments

Comments

2 Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related