Skip to content
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.

Sometimes, wrong packages are linked #60

Open
yeegor opened this issue Jul 1, 2021 · 0 comments
Open

Sometimes, wrong packages are linked #60

yeegor opened this issue Jul 1, 2021 · 0 comments

Comments

@yeegor
Copy link
Contributor

yeegor commented Jul 1, 2021

Describe the bug

The current package linking flow is as follows:

  1. go to the linkable package
  2. run npm link
  3. go to the target package
  4. run 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:)

  1. Have a CSA project with a local package named X
  2. Outside of that project, create another (different!) package with name X, run npm link on that
  3. Run dep linking in your project

Expected behavior

The package from step 1 is linked

Actual behavior

The package from step 2 is linked

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant