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
Yarn may try to optimize the dependency list and sometimes will not force updating subdepdendencies.
These RFC could be interesting yarnpkg/rfcs#71yarnpkg/rfcs#54
Looks like a bug or maybe I'm misunderstanding something
What is the current behavior?
yarn upgrade
in project that have alreadyyarn.lock
, will upgrade only the module in the command, and not upgrading the sub-modules,If the current behavior is a bug, please provide the steps to reproduce.
Lets say I have
module
lets call itmodule-0
and initspackage.json
hasIn the
package.json
for themodule-a
hasSo the dependencie looks like:
module-0
->module-a
->module-b
Now lets says that
module-a
andmodule-b
have new versionsNow I run
yarn upgrade @organization/module-a
What is the expected behavior?
I expect
module-a
andmodule-b
will be upgrademodule-a
because I asked andmodule-b
because its the sub-modulePlease mention your node.js, yarn and operating system version.
OsX El Capitan 10.11.6
node v6.10.0
yarn 0.22.0
The text was updated successfully, but these errors were encountered: