error installing due to 'dezalgo' package

I’m submitting a bug report

• Library Version: 0.32.0

Please tell us about your environment:

• Operating System: Linux (Mint 18)

• Node Version: 8.9.4

• NPM Version: 5.6.0 Current behavior: Installing via npm locally (no -g) the package fails. I’m installing with npm install aurelia-cli

1019 verbose stack Error: ENOENT: no such file or directory, rename '/home/shawn/node_modules/aurelia-cli/node_modules/npm/node_modules/dezalgo' -> '/home/shawn/node_modules/aurelia-cli/node_modules/npm/node_modules/.dezalgo.DELETE'
1020 verbose cwd /home/shawn
1021 verbose Linux 4.10.0-42-generic
1022 verbose argv "/home/shawn/node-v8.9.4-linux-x64/bin/node" "/home/shawn/bin/npm" "install" "aurelia-cli"
1023 verbose node v8.9.4
1024 verbose npm  v5.6.0
1025 error path /home/shawn/node_modules/aurelia-cli/node_modules/npm/node_modules/dezalgo
1026 error code ENOENT
1027 error errno -2
1028 error syscall rename
1029 error enoent ENOENT: no such file or directory, rename '/home/shawn/node_modules/aurelia-cli/node_modules/npm/node_modules/dezalgo' -> '/home/shawn/node_modules/aurelia-cli/node_modules/npm/node_modules/.dezalgo.DELETE'
1030 error enoent This is related to npm not being able to find a file.
1031 verbose exit [ -2, true ]

As a workaround, if I first install dezalgo (e.g. npm install dezalgo) then install the cli it works.

[fkleuver]

This is directly related to the way package-lock.json is resolved since npm@5.6.0. For aurelia-cli it happens because of the dependency on npm@3.10.8 as somewhat clarified here and here.

Possible workarounds (pick any):

• Downgrade global npm version to 5.5.1
• Delete package-lock.json and/or node_modules folder prior to npm install
• Upgrade aurelia-cli’s dependency on npm to 5.0.0 or above

As for the third option; I actually forked aurelia-cli and upgraded it’s dependency on npm to 5.6.0, did the npm link dance and I just use npm link whenever I need aurelia-cli as a dependency. The problem hasn’t occurred for me since, through multiple projects.

Is there any particular reason aurelia-cli depends on npm@^3.10.8? Otherwise why not just upgrade that dependency and be done with this silly issue?

For completeness sake, the repro:

1. npm install -g npm@5.6.0
2. Create a new folder with the following package.json: { "dependencies": {"npm": "^4.6.1" } }
3. npm install -> success
4. npm install again -> fails
5. Delete node_modules and package-lock.json, then change package.json to: { "dependencies": {"npm": "^5.0.0" } }
6. npm install -> success
7. npm install again -> success
8. npm install -g npm@5.5.1
9. Repeat steps 2-7; the difference is that step 4 will succeed

[Alexander-Taran]

world is moving towards yarn