Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
install-peerdeps fails when installing package from github, local directory, or linked package
See original GitHub issueWhen installing a package, npm lets install in these ways:
npm install <git repo url>
npm install <folder>
Would this package be interested in supporting similar syntax? Or even adding new flags?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
npx install-peerdeps npm-linked-package fails #42 - GitHub
The current behavior of this tool is that it reads peer dependencies of the specified package from the online NPM registry (or the...
Read more >Add a means to install package peer dependencies ... - GitHub
Provide a CLI command yarn install --peer which will install peer dependencies specified in package.json . That way development / testing ...
Read more >[BUG] Error installing relative paths using workspaces #3847
The workaround is to delete the node_modules folder at the root package folder. 6
Read more >Can't install dependencies when one of them is linked from ...
I guess pnpm has wrong priority adjustments: it is first looks to npm registry and only then (if at all) looks to global...
Read more >yarn link does not install package dependencies #2914 - GitHub
command should show that library has a node_modules directory with lodash installed into it. npm seems to run install on every linked package....
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
@tomprats @AquiGorka (#42) I’ve realized your issues deal with similar underlying problems so I’ve merged them here. I’ll keep this issue open for further discussion of this feature and to keep it on the roadmap; if others are also facing this problem I will prioritize it.
Thanks for taking a look and getting back to me so quickly @nathanhleung. I appreciate your hard work and your package already has helped a ton!