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
With a workspaces property defined and after yarn has been ran once, if I change the path to the sub-project but the package name itself does not change, then the symlink is not updated to the latest.
If the current behavior is a bug, please provide the steps to reproduce.
Cf current behaviour.
What is the expected behavior?
With a workspaces property defined and after yarn has been ran once, if I change the path to the sub-project but the package name itself does not change, then the symlink should be updated to the latest.
Please mention your node.js, yarn and operating system version.
yarn 1.7.0
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
bug
What is the current behavior?
With a
workspaces
property defined and after yarn has been ran once, if I change the path to the sub-project but the package name itself does not change, then the symlink is not updated to the latest.If the current behavior is a bug, please provide the steps to reproduce.
Cf current behaviour.
What is the expected behavior?
With a
workspaces
property defined and after yarn has been ran once, if I change the path to the sub-project but the package name itself does not change, then the symlink should be updated to the latest.Please mention your node.js, yarn and operating system version.
yarn 1.7.0
The text was updated successfully, but these errors were encountered: