Platform · npm
npm Fixes
Copy-paste fixes for the npm errors that stop your build. Dependency conflicts, file errors, and permission issues — the ones that make you want to delete node_modules.
Why these pages exist: npm error messages are notoriously cryptic. ERESOLVE, ENOENT, EACCES — three letters that mean nothing until you've seen them a hundred times. Each page decodes one error and gives you the fix.
🚨 Fix Pages
Something broke. Here's how to make it work again.
--force) and how to resolve it properly.sudo) takes 3 minutes.npm and the terminal says it doesn't exist. Node.js isn't installed, or PATH is misconfigured.🚧 More Coming
Growing section. Here's what's next.
📖 How to use these pages
npm errors always start with an all-caps code: ERESOLVE, ENOENT, EACCES. Match that to the page.
Every page opens with the fastest safe answer — usually a single command.
--force and --legacy-peer-deps are band-aids. The pages explain when they're OK and when they'll bite you later.