{"action":"opened","issue":{"url":"https://api.github.com/repos/npm/npm/issues/12256","repository_url":"https://api.github.com/repos/npm/npm","labels_url":"https://api.github.com/repos/npm/npm/issues/12256/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/12256/comments","events_url":"https://api.github.com/repos/npm/npm/issues/12256/events","html_url":"https://github.com/npm/npm/issues/12256","id":146586404,"number":12256,"title":"npm update --save after running npm update does not save","user":{"login":"AlexTes","id":2011351,"avatar_url":"https://avatars.githubusercontent.com/u/2011351?v=3","gravatar_id":"","url":"https://api.github.com/users/AlexTes","html_url":"https://github.com/AlexTes","followers_url":"https://api.github.com/users/AlexTes/followers","following_url":"https://api.github.com/users/AlexTes/following{/other_user}","gists_url":"https://api.github.com/users/AlexTes/gists{/gist_id}","starred_url":"https://api.github.com/users/AlexTes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AlexTes/subscriptions","organizations_url":"https://api.github.com/users/AlexTes/orgs","repos_url":"https://api.github.com/users/AlexTes/repos","events_url":"https://api.github.com/users/AlexTes/events{/privacy}","received_events_url":"https://api.github.com/users/AlexTes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-07T11:19:14Z","updated_at":"2016-04-07T11:19:14Z","closed_at":null,"body":"The documentation notes the abvo problem.\r\n> Note that npm will only write an updated version to package.json if it installs a new package.\r\nHowever that doesn't help me very much. Our unit-tests failed with a normal `npm install` with only a clean install fixing things. Because of that I'd like to force the version ranges to be at least their latest compatible version. However, as I ran a clean install, I now cannot use `npm update --save`.\r\nNeither [npm-check](https://www.npmjs.com/package/npm-check) or [npm-check-updates](https://www.npmjs.com/package/npm-check-updates) supports this, so it seems I'm dead out of luck.\r\n\r\nIs doing it all by hand / writing a script that checks mismatches between the currently installed version `npm list --depth=0` against the `package.json` the only way? Because if so, perhaps you too feel npm could be more helpful in this use-case.\r\n\r\nThanks!"}}