If you've been writing JavaScript for more than a year, you have node_modules folders all over your disk. Every cloned repo has one. Every example you tried last summer has one. Every prototype that didn't become a real project has one. They're each a few hundred megabytes to a few gigabytes, and there's probably forty of them.
You could write a one-liner to find them — find . -name node_modules -prune on Mac, a PowerShell equivalent on Windows — and then rm -rf the lot. That works, until the one repo you actively use loses its dependencies and now CI is broken because you ran the command from one folder up.
What you actually want is something visual: every node_modules on the disk, sized largest first, with the path so you can tell the actively-used ones from the abandoned ones, and a staging area so you can review the list before anything is deleted.