Solution on how to update package.json manually

[JamesVanWaza]

Solution so Far - Do It Manually

Run yarn outdated - The list of packages show up
Run yarn remove package name
Run yarn add package name

The new modules are now saved to package.json

[cpxPratik]

I use versionlens extension with visual studio code for updating dependencies on package.json. https://github.com/vscode-contrib/vscode-versionlens

[bartvanandel]

We use this solution for some of our packages as well. Seems that the yarn remove step isn't really necessary, we just do a yarn add <some_pkg(s)> and package.json gets updated.

[cpxPratik]

I do following to update package.json:

yarn global add syncyarnlock // install syncyarnlock globally
yarn upgrade // update dependencies, updates yarn.lock
syncyarnlock -s -k // updates package.json with versions installed from yarn.lock
yarn install // updates yarn.lock with current version constraint from package.json

[metasean]

Note for anyone using the syncyarnlock package —it hardcodes package versions— for example "demopackage": "^5.0.0", which would normally have an upgrade range including any version in the 5.x.x range becomes exclusively "demopackage": "5.0.1",

[cpxPratik]

@metasean , there is -k, --keepUpArrow flag to keep them, if you just read readme.