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.
Remove node_modules when switching betweeen npm & pnpm
See original GitHub issueRelated to #7461, when we detect a switch between npm/pnpm, we delete the old incompatible lock file and a new one is created.
Since npm and pnpm use a different node_modules folder structure, it would make sense to delete it after deleting the old lock file. This might take a bit longer first but would prevent bloating the disk with lots of unused files (or symlinks).
The folder should only be removed when it is detected present in the project root folder.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Wouldn’t the presence of
node_modules/.modules.yamlbe enough to detect the structure?So yes, it’s better to rely on
node_modulesstructure if possible.