Timeline for How can I forcibly exclude a nested dependency for NPM?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28 at 10:07 | comment | added | ceztko |
This strategy doesn't work properly (at least with newer npm versions). If you try to run npm i a second time without deleting package-lock.json I get the error npm error Cannot destructure property 'package' of 'node.target' as it is null., which is nasty. I'm testing the other suggested strategy but this should really be a RFE to NodeJs so it doesn't accidentally break in the future.
|
|
| Jun 24 at 19:07 | comment | added | Coderer | This doesn't seem to work. npm install just spins forever. If I specify a directory that does exist (like the path to another actually-installed dep), there is an error that the resolved dep does not match the required one. | |
| Sep 25, 2022 at 16:54 | history | answered | GOTO 0 | CC BY-SA 4.0 |