This is a "dependency tree realization" bug.
The problem here is that invoking npm rm module may cause the node_modules tree to be in an invalid state because npm rm is not dedupe aware.
npm rm module
npm i firstname.lastname@example.org -S
npm i email@example.com -S
echo "npm ls is good $?"
npm rm routes -S
echo "npm ls should be good but is bad $?"
The expected output is that the second npm ls exits zero instead of one.
Break the logic that is lib/update.js that finds all copies of module in a node_modules tree out into a function.
Then use that function to find all copies in lib/uninstall.js and then just invoke npm.commands.install for each one.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
I'm closing this as it will be fixed by the feature implemented in #6936, further discussion should happen there.
No branches or pull requests