[Question] How to include dependents of a linked package to the original project?

[Marc19]

I'm using npx link to add a symlink for a Common project of mine and use it inside Project-A and Project-B. Project-A and Project-B have a package.json that look like this:

"dependencies": {
...,
"common.ui": "file:../path-to-common-project",
...
}

I can't remember the order of steps I did but for some reason, it worked as expected once but it's not working anymore. What I mean by "it worked" is that:

• in Project-A, I did npx link ../path-to-common-project and the result was successful as shown below

• then I did npm ls --link to see the created links and this is what I found below. As you can see, the extraneous libraries that are used by the Common project were also linked. It worked as expected when I ran Project-A. I could instantly see the changes made in the Common project when I ran Project-A.

• I, then, tried to do the same steps in Project-B. So I executed npx link ../path-to-common-project successfully. Then I ran npm ls --link to see the created links but I only found that only the Common project was linked without the extraneous libraries as shown below. Also, building Project-B fails because of those missing libraries.

I first thought that Project-B has some different configuration but then I removed all the created links for Project-A by running npm unlink --no-save common.ui and tried to re-add them once again but this time it didn't work. I could only see the Common project linked without its 3rd party libraries.

Do you know why could that be the case? Am I missing something? Is there something I should do before linking a project?

[privatenumber]

Sorry, I don't really understand what you're saying.

But based on the question in the title of this issue, I think it will be solved by https://github.com/privatenumber/link/issues/13

If not, can you succinctly describe your goal/problem (without describing what you tried and what not)? Happy to re-open if different.