You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
update command calls npm update --save/--save-dev - this not only updates npm-shrinkwrap.json file (which is ok), but also package.json (which is not ok) - e.g. if one has "eslint": "*" entry in their package.json file and updates it with bundlejs update, they'll end up with "eslint": "^x.x.x" entry (with the default npm config).
Not sure what the best solution would be, either it could maybe cleanup package.json file after running update using data from .bundlerjs.json file or it could do the same as bundle install does, i.e. update everything without using --save/--save-dev options and then re-create npm-shrinkwrap.json file.
The text was updated successfully, but these errors were encountered:
Turns out that npm install --save-dev and npm update --save-dev doesn't update npm-shrinkwrap.json file... Thus, it always calls npm update --save <packages> and then recreates package.json file, so that it looks exactly the same as before running 'update' command.
update
command callsnpm update --save/--save-dev
- this not only updatesnpm-shrinkwrap.json
file (which is ok), but alsopackage.json
(which is not ok) - e.g. if one has"eslint": "*"
entry in theirpackage.json
file and updates it withbundlejs update
, they'll end up with"eslint": "^x.x.x"
entry (with the default npm config).Not sure what the best solution would be, either it could maybe cleanup
package.json
file after running update using data from.bundlerjs.json
file or it could do the same asbundle install
does, i.e. update everything without using--save/--save-dev
options and then re-createnpm-shrinkwrap.json
file.The text was updated successfully, but these errors were encountered: