NPM "ENOENT: no such file or directory error" when installing Sails.js dependencies with Node 8.9.4 LTS

Question

I recently upgraded my computer and with it, to the latest LTS version of Node and NPM:

Node.js 8.9.4
NPM 5.6.0

I have a Sails.js 0.12.14 application for which I'm trying to install NPM dependencies with npm install but when I do that, I get the following errors:

➜  web-service git:(feature/auth) ✗ npm install
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/pako-660dbb41/package.json'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/pako-660dbb41/README.md'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/pako-660dbb41/LICENSE'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/pako-660dbb41/index.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/pako-660dbb41/CHANGELOG.md'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/camelCase.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/uniqueId.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/bindKey.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/unnest.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/bindAll.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/unset.js'
// a bunch of similar Lodash errors removed from here
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/T.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/zipWith.js'
WARN tar ENOENT: no such file or directory, open '/Users/Nag/Code/project/web-service/node_modules/.staging/lodash-6e6c9f2a/fp/lastIndexOfFrom.js'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: oauth-sign@0.8.2 (node_modules/oauth-sign):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: Cannot cd into '/Users/Nag/Code/project/web-service/node_modules/.staging/oauth-sign-b13c86db'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mkdirp@0.5.1 (node_modules/mkdirp):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: Cannot cd into '/Users/Nag/Code/project/web-service/node_modules/.staging/mkdirp-c94c8047'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: minimist@0.0.8 (node_modules/mkdirp/node_modules/minimist):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: Cannot cd into '/Users/Nag/Code/project/web-service/node_modules/.staging/minimist-ba966a6e'

npm ERR! path /Users/Nag/Code/project/web-service/node_modules/.staging/sails-02afd14e/node_modules/@sailshq/body-parser
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/Users/Nag/Code/project/web-service/node_modules/.staging/sails-02afd14e/node_modules/@sailshq/body-parser' -> '/Users/Nag/Code/project/web-service/node_modules/.staging/@sailshq/body-parser-6d1e8405'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Nag/.npm/_logs/2018-01-22T14_40_13_889Z-debug.log

I can't seem to figure out what's going on and can't find suitable answers anywhere else online. I even ran npm cache clean --force, rm -rf node_modules and retried with similar errors. It seemed to work fine when I was on Node ~6 but after upgrading to Node 8.9.4 and NPM 5.6.0, it just won't install my dependencies. How can I resolve this?

Possible duplicate of [While doing npm install getting an error as "No such file or directory open"](https://stackoverflow.com/questions/52789711/while-doing-npm-install-getting-an-error-as-no-such-file-or-directory-open) — Michael Freidgeim, May 10 '19 at 13:11

score 135 · Answer 1 · answered Mar 22 '18 at 18:47

135

Try deleting the package-lock.json file.

answered Mar 22 '18 at 18:47

tantalum

2,354
1
15
22

24

I have the same issue but there is no package-lock.json – tomwang1013 May 30 '18 at 02:27
2

Weird. I assumed `package-lock.json` would fix itself instead of giving such a cryptic indirect error, but this indeed fixes that error o_o. – binki Jul 15 '18 at 20:48
we get this same thing - deleteing package-lock does "fix" the issue but prevents us from using locks. It has something to do with mapped file system permissions I think. – httpete Aug 17 '18 at 13:29
2

Nice! can you elaborate on why this is the solution? i mean what is exactly the problem here and why deleting this file is helping? – Sagiv b.g Dec 18 '18 at 17:55
Let me begin by stating that **no** elaborate engineering when into this, but here is my guess. According to the docs `package-lock.json` " It describes the exact tree that was generated, such that subsequent installs are able to generate identical trees, regardless of intermediate dependency updates." So there as an issue with that particular version of sails, but that specific version was locked in by package-lock.json. By deleting the file npm can now install an updated version that has the issue fixed.... Again this is just a guess so keep that mind. – tantalum Dec 20 '18 at 16:56
29

Doesn't deleting package-lock.json defeat the purpose of having package-lock.json? – davidtbernal Aug 14 '20 at 18:12

score 33 · Answer 2 · answered Aug 13 '19 at 13:58

33

For me, it turned out these errors were hiding the real underlying problem, which was that my credentials for a third-party npm repository (azure devops) had expired. I had to re-run vsts-npm-auth -config .npmrc to update the token in my .npmrc file.

answered Aug 13 '19 at 13:58

StriplingWarrior

151,543
27
246
315

thanks for this, expired token was the reason for me as well – Krash Sep 22 '20 at 06:56
This answer is actually the only one which really addresses the issue and doesn't only guess about solving-strategies! – nemoinho Feb 04 '22 at 11:23
1

Thanks for this. This was my issue too, I didn't have my `.npmrc` configured for Gitlab. – Philip Wigg Mar 23 '22 at 11:28

coturiv · Answer 3 · 2019-04-07T22:20:29.340

21

No permission, no internet issue, it's just a general issue of npm. I solved the problem with yarn.

yarn install

Or you can use no-optional flag.

npm install --no-optional

edited Apr 07 '19 at 22:20

answered Oct 02 '18 at 06:51

coturiv

2,880
22
39

score 15 · Answer 4 · answered Oct 13 '20 at 11:45

15

It may be a problem with the cache, try to verify the cache.

npm cache verify

answered Oct 13 '20 at 11:45

Hillgor

151
1
3

1

This solved my issue, no idea why... – Ivan Dec 17 '21 at 03:23

score 15 · Answer 5 · answered Mar 08 '21 at 13:39

15

In my case, I tried deleting package-lock.json, clearing and verifing the npm cache, removing node_modules, even stopping the antivirus (W10 machine) and was still getting this error.

I somehow fixed it by running npm update before npm install, which creates a new package-lock.json:

del /f package-lock.json
rd /s /q node_modules
npm cache clean
npm cache verify
npm update
npm install

answered Mar 08 '21 at 13:39

menrodriguez

209
3
5

After searching for hours together,this is the only solution that worked for me – Nikhil Bharadwaj May 26 '21 at 14:50
1

`npm cache clean --force` is required for npm v6+ – Chris Perry Jun 30 '22 at 22:12

score 10 · Answer 6 · answered Apr 03 '19 at 18:47

10

Deleting and regenerating 'package-lock.json' usually solves this issue however that's inherently risky because you will likely be upgrading multiple packages at a time.

In my case it turned out that there was one specific package version that package-lock.json was referencing, that was 5 levels deep in the dependency. That version no longer existed at the npm registry so it caused the install to break. I had to find which package was pulling in this dependency and upgrade that one to resolve the issue.

answered Apr 03 '19 at 18:47

jspru

1,060
1
9
17

1

Could you give more details as to how you went about this process please? – Leigh Bicknell Oct 03 '19 at 08:18
1

now i can't remember if there was a specific error that led me to the problemactic package, but there are some troubleshooting steps and tools that might help: First try this: Delete 'Node_modules'. Run 'npm i' again. Check logs for any indication of problems concerning specific packages. helpful commands: npm ls - generate a visual dependency tree (including sub dependencies) https://docs.npmjs.com/cli/ls.html npm audit - find vulnerable dependencies https://docs.npmjs.com/cli/audit Last resort: delete package-lock.json (or yarn lock) and run 'npm i'. – jspru Oct 03 '19 at 19:53

score 4 · Answer 7 · answered Apr 29 '21 at 10:26

Delete node_modules
Just delete package-lock.json file and then install packages you want with npm install . All will work.

rm -rf node_modules

rm package-lock.json

npm install
If the issue still persists check if you have a global version of any of the packages installed. This can happen if you have a global version of a package that clashes with a local version of a package.

score 3 · Answer 8 · answered Oct 25 '18 at 20:40

3

I was struggling with this for awhile, and it seems be be related to the following.

Let's say you have 3 modules, A, B and C

Module A includes B and C directly Module B also includes module C, in it's package.json dependencies.

If your package.json dependencies in module A look like the following:

"dependencies": {
     "C": "^1.0.0",
     "B": "^1.1.0"
}

You will get the above error you mentioned, ENOENT, blah, blah in .staging

If on the other hand you include the module with the nested include first like:

"dependencies": {
     "B": "^1.1.0",
     "C": "^1.0.0"
}

The error goes away. This seems like a bug in npm with nested dependencies, and the error messages and logs were not very descriptive. Check your dependency tree and see if you have the described case, if so, that is your issue.

answered Oct 25 '18 at 20:40

Severun

2,893
1
16
22

BTW, after doing the above, my package-lock.json files now work. Before I made sure all my dependencies were ordered as such, I no longer have to remove my package-lock.json files to get it to work. – Severun Oct 25 '18 at 20:41
Could you provide more details as to how to go about this process? How do you descover which modules depend on which etc? – Leigh Bicknell Oct 03 '19 at 08:20
The above worked for a bit and then came back again, after some of my team added more dependencies. One of the problems seems to be that npm installs dependencies asynchronously and depending on how you nest your dependencies, it fails in random places (because of a race condition between the async threads). For example, in the above example, if module C starts installing, then B starts installing, B will fail because it's trying to install C, which is also installing as a result of A. I just could never get npm to work 100% of the time, I switched to yarn, and have not had a problem since. – Severun Oct 08 '19 at 20:20
1

@LeighBicknell little late reply but for future readers you can use `npm ls name-of-package` which will show you the dependency tree – Mike Harrison Apr 08 '22 at 21:23

Neha Sharma · Answer 9 · 2019-04-01T13:33:08.980

3

Just delete package-lock.json file and then install package(s) you want. All will work.

edited Apr 01 '19 at 13:33

answered Nov 02 '18 at 07:57

Neha Sharma

449
5
13

score 3 · Answer 10 · answered Oct 01 '21 at 05:04

3

This happened to me when I was on Node.js 12 attempting to run npm install against a package-lock.json generated using Node.js 16.

Switching back to Node.js 16 resolved the issue:

nvm use 16

Of course, deleting the package-lock.json would have also resolved the issue for me.

answered Oct 01 '21 at 05:04

JoshuaCWebDeveloper

585
5
16

1

This seems like a probable cause in certain scenarios. I'm currently working on upgrading a repo from Node v12 to v16, and it's possible a mismatch popped up along the way. – Chris Perry Jun 30 '22 at 22:27

score 2 · Answer 11 · edited Oct 06 '20 at 00:18

2

I have presented this same error due to npm cache problems. Run

npm install --cache /tmp/empty-cache

edited Oct 06 '20 at 00:18

fcdt

2,371
5
14
26

answered Oct 05 '20 at 23:39

memartinez06

41
1

score 1 · Answer 12 · answered May 12 '20 at 10:54

1

Beside removing package-lock.json I had to remove node_modules so package-lock.json could be generated in the right way

rm -rf node_modules
rm package-lock.json
npm i

answered May 12 '20 at 10:54

Željko Šević

3,743
2
26
23

score 0 · Answer 13 · answered May 26 '21 at 08:42

0

If you dont have package-lock.json or package.json under your working folder, call npm init first.

answered May 26 '21 at 08:42

王大拿

1
2

Chris Perry · Answer 14 · 2022-07-06T04:16:24.297

0

Checkout package-lock.json from upstream and re-run `npm install`

I'm dealing with this issue right now, and it seems to have something to do with the way package-lock.json gets generated.

The problem finally resolved itself when I checked out package-lock.json from my team's upstream repository and re-ran npm install.

edited Jul 06 '22 at 04:16

answered Jun 30 '22 at 21:58

Chris Perry

6,666
3
11
21

Omkar Pai · Answer 15 · 2023-06-15T11:16:11.700

A quick checklist to solve this issue

Verify you are in the right directory with a correctly initialised npm project.
Verify you are using the correct Node and npm versions for your project then retrying npm i
Try deleting package-lock.json and then npm i.Keep in mind simply deleting package-lock.json outright might not work for some cases due to people relying on the lock behaviour, but it can lead you to the root cause.
Once you find the root cause and solve it, you can always revert back to the old package-lock.json
Verify if you are using any private packages in your package.json. Depending on the package the ~/.npmrc file might be missing or incorrectly configured.
Always be wary when deleting and regenerating package-lock.json as it can cause some confusing bugs sometimes.

Issue in my case

I was missing the ~/.npmrc file which would throw the npm WARN tar ENOENT: no such file or directory error when running npm i for a project that used private packages.
Deleting the package-lock.json and running npm i threw this error.

npm ERR! 404  '@aPrivatePackage@^2.36.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'myProject'

At this point it was clear I had to configure my .npmrc for this to work correctly as the private package required doing so.
After setting up my .npmrc and restoring the previous lock file npm i then worked correctly.

score 0 · Answer 16 · answered Jul 19 '23 at 11:33

I faced it with this issue when creating new react app via terminal.

For solving this problem;

I've previously installed create-react-app globally. I uninstall the package to ensure npx always uses the latest version of create-react-app.

To uninstall, run this command: npm uninstall -g create-react-app

After that, try to create new react app via npx create-react-app my-react-app

score 0 · Answer 17 · edited Aug 11 '23 at 19:37

0

Need to check the following:

.npmrc contains valid credentials & complete list of repos URL to download the required modules
Delete the package-lock.json file
Directory where npm install is being run, make sure it has write permission

edited Aug 11 '23 at 19:37

Tyler2P

2,324
26
22
31

answered Aug 09 '23 at 05:01

shahab alam

1
2

NPM "ENOENT: no such file or directory error" when installing Sails.js dependencies with Node 8.9.4 LTS

17 Answers17

Checkout package-lock.json from upstream and re-run `npm install`

A quick checklist to solve this issue

Issue in my case

Linked

NPM "ENOENT: no such file or directory error" when installing Sails.js dependencies with Node 8.9.4 LTS

17 Answers17

Checkout package-lock.json from upstream and re-run npm install

A quick checklist to solve this issue

Issue in my case

Linked

Checkout package-lock.json from upstream and re-run `npm install`