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
{{ message }}
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
This flow breaks on step 2 when a package with such a name already is linked. It does not get overwritten, and hence in step 4 - the old package gets linked. A possible solution for this would be to unlink the package before linking it again.
Steps to reproduce
(Write your steps here:)
Have a CSA project with a local package named X
Outside of that project, create another (different!) package with name X, run npm link on that
Run dep linking in your project
Expected behavior
The package from step 1 is linked
Actual behavior
The package from step 2 is linked
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
The current package linking flow is as follows:
npm link
npm link <linkable package **name**>
This flow breaks on step 2 when a package with such a name already is linked. It does not get overwritten, and hence in step 4 - the old package gets linked. A possible solution for this would be to unlink the package before linking it again.
Steps to reproduce
(Write your steps here:)
npm link
on thatExpected behavior
The package from step 1 is linked
Actual behavior
The package from step 2 is linked
The text was updated successfully, but these errors were encountered: