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
Results in entire contents of the foo repo in the node_modules/foo folder. I should note the same occurs when refering to a file location eg: a dependency of "foo": "../foo"
What is the expected behavior?
Should behave like npm. The node_modules/foo should only contain the files that would be contained if you did a $/dev/foo>yarn pack (ie: obey the .gitignore, .npmignore rules etc. etc.).
Please mention your node.js, yarn and operating system version.
windows 7 + yarn 0.24.4 + v6.10.0
The text was updated successfully, but these errors were encountered:
knit is an RFC that addresses a similar problem yarnpkg/rfcs#41.
Currently Yarn does not have a feature that it would pack a folder before installing it automatically.
Sounds like a good opportunity to send an RFC, I'll close the issue as there is no action I can make right now.
Do you want to request a feature or report a bug?
bug
If the current behavior is a bug, please provide the steps to reproduce.
yarn install
Results in entire contents of the foo repo in the
node_modules/foo
folder. I should note the same occurs when refering to a file location eg: a dependency of"foo": "../foo"
What is the expected behavior?
Should behave like npm. The
node_modules/foo
should only contain the files that would be contained if you did a$/dev/foo>yarn pack
(ie: obey the .gitignore, .npmignore rules etc. etc.).Please mention your node.js, yarn and operating system version.
windows 7 + yarn 0.24.4 + v6.10.0
The text was updated successfully, but these errors were encountered: