Start script fails after initial installation.
See original GitHub issueNode version: v8.1.4
npm version: 5.0.3
Operating system: macOS Sierra v10.12.5
Command line used: iTerm2
Steps to reproduce:
-
(For issue 1) 1.)
npm run setup
ornpm install
2.)npm start -s
ornpm start
-
(For issue 2) After issue 1 is resolved, run
npm start -s
ornpm start
Issue 1:
After initial installation via npm run setup
or npm install
, start script fails. Error output provided below.
Error Output:
2017-07-18 00:01 node[20270] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-07-18 00:01 node[20270] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:182
throw er; // Unhandled 'error' event
^
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1022:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1360:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-slingshot@7.0.0 test: `jest "--watch"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-slingshot@7.0.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/branden/.npm/_logs/2017-07-18T04_01_38_701Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-slingshot@7.0.0 test:watch: `npm run test -- --watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-slingshot@7.0.0 test:watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/branden/.npm/_logs/2017-07-18T04_01_38_725Z-debug.log
ERROR: "test:watch" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-slingshot@7.0.0 start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-slingshot@7.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/branden/.npm/_logs/2017-07-18T04_01_38_821Z-debug.log
Issue 2: After fixing issue 1 (see above), start script fails. Error output provided below.
Error Output:
RUNS src/components/FuelSavingsForm.spec.js
[BS] Access URLs:
-------------------------------------
Local: http://localhost:3000
External: http://192.168.0.22:3000
-------------------------------------
UI: http://localhost:3001
UI External: http://192.168.0.22:3001
-------------------------------------
[BS] Serving files from: src
[BS] Watching files...
can't resolve reference #/definitions/basicConfig from id #
can't resolve reference #/definitions/basicConfigOrBoolean from id #
PASS src/components/FuelSavingsForm.spec.jsnfigOrBoolean from id #
PASS src/components/FuelSavingsResults.spec.js
PASS src/store/store.spec.js
PASS src/reducers/fuelSavingsReducer.spec.js
PASS src/utils/fuelSavingsCalculator.spec.js
PASS src/actions/fuelSavingsActions.spec.js
PASS src/utils/mathHelper.spec.js
PASS src/components/AboutPage.spec.js
PASS src/components/FuelSavingsTextInput.spec.js
RUNS src/containers/FuelSavingsPage.spec.js
/Users/branden/Documents/GitHub/react-slingshot/tools/setup/setupPrompts.js (1/0)
✖ 6:28 Unnecessary escape character: \. no-useless-escape
✖ 1 error (12:05:24 AM)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-slingshot@7.0.0 lint: `esw webpack.config.* src tools --color`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-slingshot@7.0.0 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/branden/.npm/_logs/2017-07-18T04_05_24_348Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-slingshot@7.0.0 lint:watch: `npm run lint --watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-slingshot@7.0.0 lint:watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/branden/.npm/_logs/2017-07-18T04_05_24_377Z-debug.log
ERROR: "lint:watch" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-slingshot@7.0.0 start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-slingshot@7.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/branden/.npm/_logs/2017-07-18T04_05_24_482Z-debug.log
Issue Analytics
- State:
- Created 6 years ago
- Comments:38 (12 by maintainers)
Top Results From Across the Web
Start script missing error when running npm start
App with the scripts was in folder B. Folder B was in folder A. I open folder A in vscode and enter "npm...
Read more >Error Message "Failed to Run Install Script"
From the Windows Desktop, click on the Start Button, (XP) click Run (Vista) type Run into the Start Search box and choose Run...
Read more >32-bit install from Startup Script fails on 64-bit machines - ITNinja
Nothing happens if they are already installed; the script just exits. The scripts work PERFECTLY from the command line and as Startup Scripts...
Read more >failure to install as startup script - EViews.com
I have two patch files for it, but they don't apply since the initial program hasn't installed. Oddly, they ALSO exit with errorlevel...
Read more >Troubleshoot Errors During or After Upgrading Salesforce CPQ
The Salesforce CPQ package installed correctly but the post-install script failed. Please review the error messages, make the necessary ...
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
For those still having this issue I recently, setup a new laptop with
react-slingshot
.https://gist.github.com/kwelch/618a156d9aa7e1702f6b3cd2e6abc5b2 (The prop-types part has been fixed with the recent merge of the React 16 upgrade)
The believe I ran across the same issue as others in this thread and installing watchman fixed the issue completely.
Hey @DaneTheory and @coryhouse myself and another developer were receiving this error as well. We found out that
watchman
is required / a dependency, but not annotated in your docs. After runningbrew install watchman
the build works as intended.