How to exclude several dependencies from hoisting?
See original GitHub issueCould I do something like --nohoist=node-pty|electron-rebuild
?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Is there a way to exclude a specific package from hoisting in ...
To hoist nothing, you may set hoist=false in .npmrc . To hoist only the babel packages, you may set hoist-pattern[]=@babel/*.
Read more >nohoist in Workspaces | Yarn Blog
“nohoist” enables workspaces to consume 3rd-party libraries not yet compatible with its hoisting scheme. The idea is to disable the selected ...
Read more >Manage build dependencies | Netlify Docs
Specify dependencies for your project so that our platform can install required ... You can override this by adding --no-ignore-optional to this variable....
Read more >npm-install - npm Docs
By default, npm install will install all modules listed as dependencies in ... If set to false, then ignore package-lock.json files when installing....
Read more >Advanced package manager features for npm, Yarn, and pnpm
In such situations, hoisting can lead to phantom dependencies and doppelgangers. ... .yarnrc.yml # alternatively, remove the next two lines, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
--nohoist
is effectively an implicit negation. You can pass as many--nohoist=<glob>
arguments as you want, they’ll be iterated in order to filter the list. The glob itself should match the package name, not directory or any other value.Alternatively, you can provide an array under
command.bootstrap.nohoist
inlerna.json
:This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.