npm install --save isn't writing to package.json after manual delete #15448

thebenwaters opened this Issue Jan 11, 2017 · 2 comments


None yet

3 participants


I'm opening this issue because:

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

What's going wrong?

I'm trying to do
Also i'm doing this because the server runs out of server with the package in it with the dependencies.

sed delete package from package.json
npm install
npm install --save package (the same one deleted from the line)

Then the package isn't written to the package.json

How can the CLI team reproduce the problem?

supporting information:

  • npm -v prints:
  • node -v prints:
  • npm config get registry prints:
  • Windows, OS X/macOS, or Linux?: Ubuntu 14.04
  • 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.
    • [X ] I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).

Cannot reproduce on npm@4.1.1. Try updating to latest.

KenanY commented Jan 18, 2017

Closing as abandoned.

@KenanY KenanY closed this Jan 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment