-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does Yalc resolve dependencies as if I npm installed the local module? #50
Comments
You mean after you installed then B somewhere? if your B package will contain |
This question may have been misread. From a look at the code, it seems that the dependencies of package "A" are not resolvable when a consuming package "B" uses For example, if both of these are true:
..then this is also true:
|
I assume the intention was for users to run |
The following should be added to the docs:
Then, we should change I'll be working on a PR sometime soon, so LMK what you think @whitecolor. |
Hmm, actually, it might be best to run PS: I'm curious, why does |
I agree, this is the workflow I ended up using. I'm not a fan of installing the |
I am hitting this issue with Next.js + Storybook, must admit it's confusing at first. I'd rather had (non minimal) reproduction here: https://github.com/lbke/next-plugin-storybook-demo, if you don't I am not knowledgeable enough to fully grasp what happens, but it doesn't seem to behave like an Note I am using |
Was this issue ever resolved? I'm having a very similar issue. When I run |
Im having the same issue as described above, can this get a higher priority ? |
I wouldn't bet on that. |
Let's say I have two packages A and B. B depends on A. I use yalc to add A to B, will yalc resolve A's dependencies into B's node_modules folder (as if I npm installed A)?
The text was updated successfully, but these errors were encountered: