A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Memes and software development shitposting
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
Web design, graphic design and everything in-between
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
Have been using yarn upgrade --exact. The flag forces the command to override package.json no matter how the version constraint is declared.
yarn upgrade --exact
package.json
yarn upgrade react --latest --exact
Actually, discovered that sometimes package.json is not being updated.
Looks like yarn add is more reliable than yarn upgrade:
yarn add
yarn upgrade
yarn add react --exact
The downside it will install a new package if it has not been installed yet.
This technique can be used to upgrade all packages in a given scope:
jq -r '.dependencies | keys | .[] | select(startswith("@myscope/"))' package.json | xargs yarn add --exact
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Have been using
yarn upgrade --exact
. The flag forces the command to overridepackage.json
no matter how the version constraint is declared.Actually, discovered that sometimes
package.json
is not being updated.Looks like
yarn add
is more reliable thanyarn upgrade
:The downside it will install a new package if it has not been installed yet.
This technique can be used to upgrade all packages in a given scope: