No such file or directory renaming .dezalgo.DELETE

[lesander]

Hi there!

When installing/updating a project of mine using npm install, I ran across the following problem with dezalgo:

npm ERR! enoent ENOENT: no such file or directory, rename '/Users/sander/Repositories/project/node_modules/npm/node_modules/dezalgo' -> '/Users/sander/Repositories/project/node_modules/npm/node_modules/.dezalgo.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.

This seems to have occured out of the blue, so I wondered if this has anything to do with the dezalgo package?

---

Full debug log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'i',
1 verbose cli   '--reinstall' ]
2 info using npm@5.6.0
3 info using node@v9.2.0
4 verbose npm-session 09a7132d3aa76b8c
[...]
15 silly idealTree project@0.0.0
15 silly idealTree ├─┬ npm@4.4.1
15 silly idealTree │ ├── dezalgo@1.0.3
[...]
18 silly diffTrees add dezalgo@1.0.3
[...]
25 silly decomposeActions preinstall dezalgo@1.0.3
26 silly decomposeActions build dezalgo@1.0.3
27 silly decomposeActions install dezalgo@1.0.3
28 silly decomposeActions postinstall dezalgo@1.0.3
29 silly decomposeActions finalize dezalgo@1.0.3
30 silly decomposeActions refresh-package-json dezalgo@1.0.3
[...]
70 silly finalize /Users/sander/Repositories/project/node_modules/npm/node_modules/dezalgo
[...]
72 silly saveTree project@0.0.0
72 silly saveTree ├─┬ jquery@3.3.0
72 silly saveTree │ ├─┬ npm@4.4.1
72 silly saveTree │ │ ├─┬ dezalgo@1.0.3
[...]
74 verbose stack Error: ENOENT: no such file or directory, rename '/Users/sander/Repositories/project/node_modules/npm/node_modules/dezalgo' -> '/Users/sander/Repositories/project/node_modules/npm/node_modules/.dezalgo.DELETE'
75 verbose cwd /Users/sander/Repositories/project
76 verbose Darwin 17.3.0
77 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "--reinstall"
78 verbose node v9.2.0
79 verbose npm  v5.6.0
80 error path /Users/sander/Repositories/project/node_modules/npm/node_modules/dezalgo
81 error code ENOENT
82 error errno -2
83 error syscall rename
84 error enoent ENOENT: no such file or directory, rename '/Users/sander/Repositories/project/node_modules/npm/node_modules/dezalgo' -> '/Users/sander/Repositories/project/node_modules/npm/node_modules/.dezalgo.DELETE'
85 error enoent This is related to npm not being able to find a file.
86 verbose exit [ -2, true ]

[aSegatto]

Same problem for me !

[Tang8330]

#6

[ngood97]

I solved this problem by updating npm in my package.json to 5.6.0 (npm/npm#17444 (comment))

Update: I just ran into this issue again while running the now most recent version of npm and discovered that installing any dependencies with an older version of npm as a requirement also caused this error for me (npm-check-updates requires npm 3.10.10)

[vatsalpande]

I am already on version 5.6 and still facing this issue

[ogezue]

Still not fixed. Some dependy of mine is using dezalgo. --> Project build failing

[korczis]

@ogezue deleting package-lock.json then reinstalling works for me.

[marco-fp]

Same here, deleting package-lock.json and node_modules didn't work.

[gelevanog]

Guys, try to delete npm-check-updates dependency if it's installed. This should help

[danawoodman]

I can verify that removing npm-check-updates fixed this for me. I assume it is an issue with that package instead?

Looks like it is an issue submitted here: raineorshine/npm-check-updates#420

[alittletf]

@marco-fp You ever get a fix? I am running into the same issue and deleting package-lock.json and node_modules did not work for me either...

[tmadison-gpsw]

node 8.9.4
npm 5.6.0

It looks like this is happening with npm link as well...

Running rm -rf node_modules/npm before running npm link fixes it.

[Manimall]

i think it's gonna be a decision//// npm i -g npm ////

[run1t]

I had the same problem on:
node 9.8.0
npm 5.60

Updating npm to 5.7.1 seems to fix the problem.

[rebase-master]

Same problem

node 9.9.0
npm 5.6.0

Running rm -rf node_modules and npm i again fixes it but it's not the solution.

[mattc41190]

The node_modules two step work for me. Yuck.

rm -r node_modules
npm i

[smoebody]

I identified the depending package with

#$ npm ls dezalgo
..
`-- npm-check-updates@2.12.0
  `-- npm@3.10.10
    +-- UNMET DEPENDENCY dezalgo@1.0.3
    +-- read-package-tree@5.1.5
    | `-- UNMET DEPENDENCY dezalgo@1.0.3
    +-- readdir-scoped-modules@1.0.2
    | `-- UNMET DEPENDENCY dezalgo@1.0.3
    `-- UNMET DEPENDENCY realize-package-specifier@3.0.3
      `-- UNMET DEPENDENCY dezalgo@1.0.3

npm ERR! missing: dezalgo@1.0.3, required by npm@3.10.10
npm ERR! missing: realize-package-specifier@3.0.3, required by npm@3.10.10
npm ERR! missing: dezalgo@1.0.3, required by read-package-tree@5.1.5
npm ERR! missing: dezalgo@1.0.3, required by readdir-scoped-modules@1.0.2
npm ERR! missing: dezalgo@1.0.3, required by realize-package-specifier@3.0.3

and removed npm-check-updates.

#$ npm uninstall npm-check-updates

Then I triggered install again

#$ npm install

and it finished successfully

[Mathijs003]

I had this issue too using npm v5.6.0, upgraded to 6.0.0 and now every installation works fine.

run npm i -g npm to upgrade

[Primajin]

as @danawoodman suggested, it worked best for me to just remove check updates, upgrade npm and then reinstall it

[litchian18]

deleting package-lock.json then reinstalling works for me.

[crobinson42]

I had this issue too using npm v5.6.0, upgraded to 6.0.0 and now every installation works fine.

run npm i -g npm to upgrade

[ehxxn]

A simple Logical solution.
use Yarn instead