How can I avoid yarn generating symlinks to my internal packages???? #5801
MikeMitterer
started this conversation in
General
Replies: 1 comment 1 reply
-
I assume If you want to fetch these packages externally (e.g. from npm) you can disable transparent workspaces. Do note that this means changes to a local workspace won't be visible to other workspaces until you publish them externally (e.g. to npm). Any packages that you do want to symlink need to be declared using |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This drives me crazy! In my .yarnrc.yml I've set
nmHoistingLimits: dependencies
witch works really nice and does what I want. The only exception is that yarn (4.0.0-rc.53) symlinks my internal packages. If one of these packages is not built on this machine (if there is no lib/dist folder) I get all kind of crazy errors.Beta Was this translation helpful? Give feedback.
All reactions