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
Do you want to request a feature or report a bug?
Feature
What is the current behavior? yarn upgrade-interactive only lists top-level dependencies
What is the expected behavior?
Would be nice to also list transitive dependencies, possibly behind an option?
This would allow bumping the version of a transitive dependency in the lockfile to a newer version which still satisfies the various version ranges, but without adding it into package.json.
Please mention your node.js, yarn and operating system version.
v0.19.1
The text was updated successfully, but these errors were encountered:
After poking around a bit more, I think this a slightly wider "issue". Its unclear to me how new versions of transitive dependencies should be incorporated into the dependency tree at all - regardless of whether this command can be expanded to support this behaviour.
Is there a way to do do this other than manually editing yarn.lock?
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
yarn upgrade-interactive
only lists top-level dependenciesWhat is the expected behavior?
Would be nice to also list transitive dependencies, possibly behind an option?
This would allow bumping the version of a transitive dependency in the lockfile to a newer version which still satisfies the various version ranges, but without adding it into package.json.
Please mention your node.js, yarn and operating system version.
v0.19.1
The text was updated successfully, but these errors were encountered: