Unable to run the boilerplate after running setup and running npm start
See original GitHub issueUnable to run boilerplate using version 7.
`internal/child_process.js:325 throw errnoException(err, ‘spawn’); ^
Error: spawn EACCES at _errnoException (util.js:1041:11) at ChildProcess.spawn (internal/child_process.js:325:11) at Object.exports.spawn (child_process.js:493:9) ` Environment details: Node version: 8.4.0
npm version: 5.4.0
Operating system: Ubuntu 16.4 LTS
Command line used: npm start
Steps to reproduce: 1) clone react-slingshot, 2) run “npm run setup” 3) run “npm start -s”
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (1 by maintainers)
Top Results From Across the Web
NPM run setup not working · Issue #2603 - GitHub
Description. An error occurs when trying to install the modules dependencies via the command npm run setup.
Read more >Error while executing 'npm install' in aspnet boilerplate react ...
You have a dependency conflict (incorrect and possibly broken dependency), so try using --force , or run the command --legacy-peer-deps .
Read more >ts-node - npm
This error is thrown by node when a module is require() d, but node believes it should execute as native ESM. This can...
Read more >Troubleshooting - Create React App
When you save a file while npm start is running, the browser should refresh with the updated code. If this doesn't happen, try...
Read more >Creating a React App - Codecademy
We will use npx, a package runner tool that comes with npm 5.2+ and higher, to install and run create-react-app . This will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Had the same issue on OSX. Installing watchman helped.
brew install watchman
Installing watchman fixed it for me on OSX as well.