[FR] Install peerdeps from local package
See original GitHub issueDon’t know if this isn’t already possible, but I’d like to be able to install peerdeps globally from a local package.
I have a local package (eslint-config-sarpik) which I have installed globally (not via linking (should I just use linking?)).
Sometimes I add some peerDependencies & I’d like to be able to install them myself globally prior to publishing.
Being able to do something like npx install-peerdeps --global --yarn ./
would be awesome.
See also https://github.com/nathanhleung/install-peerdeps/pull/51 for locally linked packages.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7
Top Results From Across the Web
install-peerdeps - npm
Start using install-peerdeps in your project by running `npm i ... There are 24 other projects in the npm registry using install-peerdeps.
Read more >How to install npm peer dependencies automatically?
Yes, to second @drizzd comment: npm-install-peers is only intended for installing the "peerDependencies" listed in your project's package.json.
Read more >install-peerdeps | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >you must install peer dependencies yourself Code Example
You must install peer dependencies yourself. npm install requires a peer of · npm package version controler for peer dependencies · npm peer...
Read more >How to handle peer dependencies when developing modules
Tagged with javascript, react, yarn, peerdependencies. ... yarn and npm don't provide tools to install peer dependencies for your ...
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
I’m just trying to test a shared config myself before publishing to make sure it works.
Doesn’t matter though - I figured I’ll just use
yarn link
. Thank you for your time & help:)I’m not sure what you mean. If you want to test a shared config before publishing, you’d npm link it, and each of its peer deps, into another project (or, install it from git in the other project).