"npm i" sets the "version" field of installed node_modules to the dist link instead of the version number.

[VamshiKrishnaAlladi]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

With npm@5.0.3, when I install a package, the version number field in the package.json has the link to npm registry instead of the actual version number.

Is this by design? or is something going wrong here?

If it is by design, isn't the field name misleading?

How can the CLI team reproduce the problem?

By installing any package.

supporting information:

• npm -v prints: 5.0.3
• node -v prints: 8.1.1
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Win10
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[VamshiKrishnaAlladi]

Any update on this?

[VamshiKrishnaAlladi]

Is anyone looking into it? All my CI builds are failing.

[VamshiKrishnaAlladi]

Is anyone even looking into this? All I see here are tumble weeds. 😢

[zkat]

Is this still happening in the latest npm? (5.3.0)

[VamshiKrishnaAlladi]

Yeah. I've just verified it's happening in 5.3.0 as well.

The above screenshot is of one of the node_module's package.json.

The version field here has a link and the Circle CI builds fails at a sem-ver check saying "invalid field value for version". My local builds run normally though.

[zkat]

@VamshiKrishnaAlladi I really wonder how to repro this. I wonder if you just have old results cached or something. This is probably the root cause of #17858, too.

[VamshiKrishnaAlladi]

@zkat You do not see this when you install a module?