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
We could also have installation algorithms that prioritise installed version over last available version (related to #118)
What alternatives have you considered?
On small projects, I delete the lock and start from a fresh install.
On larger project with tens of dependencies used in production, I keep using yarn so that I can safely bump a dev dependency and then deduplicate the install of esbuild for example without touching the exact version of my UI dependencies.
The text was updated successfully, but these errors were encountered:
What is the problem this feature will solve?
Reduce the total number of installed dependencies after a adding/bumping a dependency.
Example:
First installed:
module-a
requestesbuild ^0.15.7
,module-b
requestesbuild ^0.15.8
esbuild v0.15.10
is installedFew days later, bumping
module-a
, still requestesbuild ^0.15.7
Both
esbuild v0.15.10
andesbuild v0.15.11
are installedWhat is the feature you are proposing to solve the problem?
Builtin version of https://github.com/scinos/yarn-deduplicate
We could also have installation algorithms that prioritise installed version over last available version (related to #118)
What alternatives have you considered?
On small projects, I delete the lock and start from a fresh install.
On larger project with tens of dependencies used in production, I keep using yarn so that I can safely bump a dev dependency and then deduplicate the install of esbuild for example without touching the exact version of my UI dependencies.
The text was updated successfully, but these errors were encountered: