Error: spawn EACCES
Node tried to execute a file that isn’t executable (missing +x permission) or isn’t a program.
spawn EACCES Meaning
Bundled binaries (esbuild, puppeteer Chrome, scripts) lose their execute bit when copied from Windows/zip archives or installed with --no-bin-links.
Common causes
- Binary without execute permission
- Spawning a script without a shebang
- Mount with noexec (Docker volumes, /tmp)
⚡ Quick fix
- chmod +x the binary
- Reinstall the package (rm -rf node_modules && npm ci)
- Avoid noexec mounts
Detailed fix by platform
Linux
chmod +x node_modules/.bin/* node_modules/esbuild/bin/esbuild
How to diagnose
- File — Which executable?
- Mode — ls -l shows x?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 229 SQL Server Msg 229: The SELECT permission was denied on the object
- 5123 SQL Server Msg 5123: CREATE FILE encountered operating system error 5 (Access is denied) while attempting to open the physical file
- 916 SQL Server Msg 916: The server principal is not able to access the database under the current security context
Most viewed in Node.js
- nodemon crashed [nodemon] app crashed - waiting for file changes before starting...
- MODULE_NOT_FOUND Error: Cannot find module 'x' (MODULE_NOT_FOUND)
- UnhandledPromiseRejection Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026