Can't install with npm 3.5.2

[drewcovi]

Reproduction

1. Create folder
2. npm install ember-data
3. See output below

Description

Running on Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-65-generic x86_64)

➜  testing npm install --save-dev ember-data
npm ERR! addLocal Could not install /home/drew/testing/@ember-data/[email protected]
npm ERR! Linux 4.15.0-65-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "--save-dev" "ember-data"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! path /home/drew/testing/@ember-data/[email protected]
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open

npm ERR! enoent ENOENT: no such file or directory, open '/home/drew/testing/@ember-data/[email protected]'
npm ERR! enoent ENOENT: no such file or directory, open '/home/drew/testing/@ember-data/[email protected]'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! Please include the following file with any support request:
npm ERR!     /home/drew/testing/npm-debug.log

Debug log

https://gist.github.com/drewcovi/e1aa549e8dafaee6e104e17c10f4e8e3

[drewcovi]

Resolving here should resolve issues in ember init emberjs/ember.js#18473 (comment)

[rwjblue]

Thank you for helping dig into this @drewcovi!

[rwjblue]

Hmm, why does your system have [email protected]? [email protected] comes with [email protected] bundled by default 🤔

[drewcovi]

Can't say, just fired up apt install nodejs npm but ill look into it. would love to know what changed between the npm versions that impacted this.

[runspired]

@rwjblue @drewcovi closing as a duplicate/wont-fix. The issue here is with folks using Verdaccio. verdaccio/verdaccio#1429

[runspired]

(as an aside, if there is an issue with older npm we aren't aware of we also can't fix older npm)

[rwjblue]

Hmm, @runspired what points to the verdaccio issue in this report?

[runspired]

also related: #6273

[rwjblue]

@drewcovi - Can double check if you are using verdaccio in your environment?

[runspired]

Looking further at the log it does seem this is an issue with outdated npm similar to the issues verdaccio encountered but distinct:

360 silly resolveWithNewModule @ember-data/[email protected] checking installable status
361 silly cache add args [ '@ember-data/[email protected]', null ]
362 verbose cache add spec @ember-data/[email protected]
363 silly cache add parsed spec Result {
363 silly cache add   raw: '@ember-data/[email protected]',
363 silly cache add   scope: '@ember-data',
363 silly cache add   name: '@ember-data/model',
363 silly cache add   rawSpec: '3.13.1',
363 silly cache add   spec: '3.13.1',
363 silly cache add   type: 'version' }
364 silly addNamed @ember-data/[email protected]

note the parsing above on @ember-data/model, then see how @ember-data/-build-infra is not parsed for name and scope correctly

113 silly fetchOtherPackageData @ember-data/[email protected]
114 silly cache add args [ '@ember-data/[email protected]', null ]
115 verbose cache add spec @ember-data/[email protected]
116 silly cache add parsed spec Result {
116 silly cache add   raw: '@ember-data/[email protected]',
116 silly cache add   scope: null,
116 silly cache add   name: null,
116 silly cache add   rawSpec: '@ember-data/[email protected]',
116 silly cache add   spec: '/home/drew/testing/@ember-data/[email protected]',
116 silly cache add   type: 'local' }
117 error addLocal Could not install /home/drew/testing/@ember-data/[email protected]
118 silly fetchPackageMetaData Error: ENOENT: no such file or directory, open '/home/drew/testing/@ember-data/[email protected]'
118 silly fetchPackageMetaData  error for @ember-data/[email protected] { Error: ENOENT: no such file or directory, open '/home/drew/testing/@ember-data/[email protected]'
118 silly fetchPackageMetaData   errno: -2,
118 silly fetchPackageMetaData   code: 'ENOENT',
118 silly fetchPackageMetaData   syscall: 'open',
118 silly fetchPackageMetaData   path: '/home/drew/testing/@ember-data/[email protected]' }

[runspired]

Incidentally the folks at verdaccio had designed their system around npm's perceived limitation around dashes: verdaccio/verdaccio#1400

verdaccio/verdaccio#1409

[drewcovi]

@runspired @rwjblue definitely not using verdaccio at all... this was on a clean system. Considering that the package for Ubuntu LTS is still 3.5.2 is this still closed as a wont fix?

[drewcovi]

Or if I understand the issue, it has more to do with the actual name of the repository which would be the only fix here since npm holds the keys to this fix

[drewcovi]

If so, should there be a clear requirement for npm version in the Ember docs?

[runspired]

Or if I understand the issue, it has more to do with the actual name of the repository which would be the only fix here since npm holds the keys to this fix

Correct. The version of npm you have does not appear to support scoped packages with dashes starting the name following the scope

If so, should there be a clear requirement for npm version in the Ember docs?

There is via node version requirement. It is unfortunate that some platforms provide a different version of npm than that bundled.