yarnpkg/yarn

Workspaces - Is it possible to exclude some node_modules from beeing hoisted to the root node_modules folder?

Open

#3.882 geöffnet am 10. Juli 2017

Auf GitHub ansehen
 (41 Kommentare) (52 Reaktionen) (0 zugewiesene Personen)JavaScript (2.731 Forks)batch import
cat-featurehelp wantedhigh-priorityneeds-discussiontriaged

Repository-Metriken

Stars
 (41.514 Stars)
PR-Merge-Metriken
 (Keine gemergten PRs in 30 T)

Beschreibung

Do you want to request a feature or report a bug? Feature

What is the current behavior? We are currently using hoist feature from lerna. I tried to move to yarn workspaces and it works way faster! Awesome, thank you!

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior? But i also need the ability (sadly) to exclude some node_modules from not beeing hoisted to the root node_modules folder but be physically installed in the package i configured it as dependency. (The same way the --no-hoist arguments are working for lerna. ) The reason is, sadly, that some dependencies we use, are trying to require some dependencies with an absolute path from packages/<package>/node_modules directly. So i have to exclude some. Is there a way to configure some sort of exclude glob for workspaces?

Please mention your node.js, yarn and operating system version. yarn --version: 0.27.5 node -v: v6.11.0 macOS: 10.12.5

Contributor Guide