Start script fails after initial installation. #449

DaneTheory · 2017-07-18T04:24:18Z

Node 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 or npm install
2.) npm start -s or npm start
(For issue 2)
After issue 1 is resolved, run
npm start -s or npm 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! [email protected] test: `jest "--watch"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! [email protected] test:watch: `npm run test -- --watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! [email protected] lint: `esw webpack.config.* src tools --color`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! [email protected] lint:watch: `npm run lint --watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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

The text was updated successfully, but these errors were encountered:

Issue 1: Removed extra dashes located in the package.json test scripts that cause start script to fail. Issue 2: Removed escape characters found in setupPrompts.js which cause linting to fail, thus breaking start script.

DaneTheory · 2017-07-18T04:41:44Z

Fix provided in PR
#450

coryhouse · 2017-07-18T11:24:03Z

Thanks Dane! I just added Jest CLI as a dev dependency to resolve issue 1. a5cf0e0

If you back out your changes to package.json in the PR, then I'll merge the changes for issue 2.

Thanks! 👍

DaneTheory · 2017-07-18T13:56:11Z

Should have read this before responding to the PR. Whoops! Thanks, removing the dashes change now.

Removed change that removed additional dashes in npm test scripts in favor of adding jest-cli as a devDep. This commit instead focusses on issue 2 from coryhouse#449 where setupPrompts.js had a bug that caused start script to fail.

Removed change that removed additional dashes in npm test scripts in favor of adding jest-cli as a devDep. This commit instead focusses on issue 2 from #449 where setupPrompts.js had a bug that caused start script to fail.

alexmattorr · 2017-07-19T18:17:12Z

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 running brew install watchman the build works as intended.

kwelch · 2017-07-19T18:53:48Z

The conversation about watchman was discussed in #437. Although it is a dependency it is not a direct dependency since it is only required for jest. A PR would be appreciated to update the docs to accurately reflect this.

jonasfrid · 2017-07-22T19:35:50Z

@DaneTheory may I ask how you fixed issue #1 above? I'm stuck with the same issue.
Node version:
v6.11.1

npm version:
3.10.10

Operating system:
macOS Sierra v10.12.5

Determining test suites to run...2017-07-22 21:47 node[32781] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-07-22 21:47 node[32781] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: Error watching file for changes: EMFILE
    at exports._errnoException (util.js:1018:11)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1420:11)

npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "test" "--" "--watch"
npm ERR! node v6.11.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] test: `jest "--watch"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test script 'jest "--watch"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the test-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     jest "--watch"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs test-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls test-app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jonas/Sites/br/react-slingshot/npm-debug.log

npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/bin/npm-cli.js" "run" "test:watch"
npm ERR! node v6.11.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] test:watch: `npm run test -- --watch`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test:watch script 'npm run test -- --watch'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the test-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run test -- --watch
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs test-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls test-app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jonas/Sites/br/react-slingshot/npm-debug.log
ERROR: "test:watch" exited with 1.

npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.11.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script 'npm-run-all --parallel test:watch open:src lint:watch'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the test-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-run-all --parallel test:watch open:src lint:watch
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs test-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls test-app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jonas/Sites/br/react-slingshot/npm-debug.log

coryhouse · 2017-07-23T13:02:30Z

@jonasfrid - Did you install watchman as described in this thread?

brew install watchman

jonasfrid · 2017-07-24T04:46:17Z

I did npm install watchman

On Sun, 23 Jul 2017 at 15:02, Cory House ***@***.***> wrote: @jonasfrid <https://github.com/jonasfrid> - Did you install watchman as described in this thread? brew install watchman — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#449 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AM6UrzDmGJooCgJ-2zgDKIkS4-u72ITqks5sQ0RrgaJpZM4Oa1An> .

-- Sent from Gmail Mobile

DaneTheory · 2017-07-24T14:54:01Z

@jonasfrid were you able to get things working? I got it working by removing the dashes added in the NPM test related scripts. @coryhouse fixed the bug by adding jest-cli as a local dependency. Try cloning a fresh copy of the master repo and building it anew. Everything should work.

andrespontt · 2017-08-05T23:06:05Z

just cloned and after setup & run and I got the same error.
OS: macOS 10.12.6
terminal: iterm2+zhs+zhs-completion

nickytonline · 2017-08-06T02:36:51Z

@andrespontt, what version of Node are you running? Can you also just paste the full error log you got? Thanks.

kwelch · 2017-08-06T02:53:57Z

@nickytonline We may want to set our jest to not use watchman and update docs to explain that the test script can be faster if you install watchman and change the settings.

DaneTheory · 2017-08-06T13:18:29Z

@kwelch I agree, though a more elegant solution would be one which doesn't require a new/existing user to dig around the docs just to get the start scripts up and running.

DaneTheory · 2017-08-06T13:23:46Z

@andrespontt were you able to find a fix? If not, could you provide the info requested in the docs for making a proper Issue ticket? Thanks! i.e.

Node version
npm version
Operating System
Command line used
Steps to reproduce
Error Output

andrespontt · 2017-08-06T13:55:35Z

@DaneTheory @nickytonline
Node and NPM version

{ 'react-slingshot': '7.0.0',
  npm: '5.3.0',
  ares: '1.10.1-DEV',
  http_parser: '2.7.0',
  icu: '58.2',
  modules: '48',
  node: '6.11.2',
  openssl: '1.0.2l',
  uv: '1.11.0',
  v8: '5.1.281.103',
  zlib: '1.2.11' }

System Operating &Hardware Overview:

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro14,2
  Processor Name:	Intel Core i5
  Processor Speed:	3.1 GHz
  System Version:	macOS 10.12.6 (16G29)
  Kernel Version:	Darwin 16.7.0

Command line used
npm start
Steps to reproduce

git clone https://github.com/coryhouse/react-slingshot.git
cd react-slingshot
npm run setup 
npm start

Error output

can't resolve reference #/definitions/basicConfig from id #
can't resolve reference #/definitions/basicConfigOrBoolean from id #
can't resolve reference #/definitions/basicConfigOrBoolean from id #
2017-08-06 09:52 node[56338] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-08-06 09:52 node[56338] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: Error watching file for changes: EMFILE
    at exports._errnoException (util.js:1020:11)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1420:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test: `jest "--watch"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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/andrespontt/.npm/_logs/2017-08-06T13_52_06_237Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test:watch: `npm run test -- --watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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/andrespontt/.npm/_logs/2017-08-06T13_52_06_304Z-debug.log
ERROR: "test:watch" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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/andrespontt/.npm/_logs/2017-08-06T13_52_06_431Z-debug.log

startup.txt

DaneTheory · 2017-08-06T14:04:26Z

@andrespontt Not seeing anything that stands out right away. Could you post the output from /Users/andrespontt/.npm/_logs/2017-08-06T13_45_40_380Z-debug.log
Only thing consistent with this issue is running on OSX.

I'll take a look at the log output. While I'm doing that, have you tried reproducing my fix for this mentioned here:
#450

Code diff found here:
6c54e55

Let me know what you end up with. Thanks. We'll figure this out.

andrespontt · 2017-08-06T14:08:49Z

@DaneTheory Thanks for the quick response. I'll try the #450 fix

Output /Users/andrespontt/.npm/_logs/2017-08-06T13_45_40_380Z-debug.log

 cat /Users/andrespontt/.npm/_logs/2017-08-06T13_45_40_380Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 verbose lifecycle [email protected]~prestart: unsafe-perm in lifecycle true
7 verbose lifecycle [email protected]~prestart: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/andrespontt/github/react-slingshot/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
8 verbose lifecycle [email protected]~prestart: CWD: /Users/andrespontt/github/react-slingshot
9 silly lifecycle [email protected]~prestart: Args: [ '-c', 'npm-run-all --parallel start-message' ]
10 silly lifecycle [email protected]~prestart: Returned: code: 0  signal: null
11 info lifecycle [email protected]~start: [email protected]
12 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
13 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/andrespontt/github/react-slingshot/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
14 verbose lifecycle [email protected]~start: CWD: /Users/andrespontt/github/react-slingshot
15 silly lifecycle [email protected]~start: Args: [ '-c',
15 silly lifecycle   'npm-run-all --parallel test:watch open:src lint:watch' ]
16 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
17 info lifecycle [email protected]~start: Failed to exec start script
18 verbose stack Error: [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
18 verbose stack     at emitTwo (events.js:106:13)
18 verbose stack     at EventEmitter.emit (events.js:191:7)
18 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
18 verbose stack     at emitTwo (events.js:106:13)
18 verbose stack     at ChildProcess.emit (events.js:191:7)
18 verbose stack     at maybeClose (internal/child_process.js:891:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
19 verbose pkgid [email protected]
20 verbose cwd /Users/andrespontt/github/react-slingshot
21 verbose Darwin 16.7.0
22 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
23 verbose node v6.11.2
24 verbose npm  v5.3.0
25 error code ELIFECYCLE
26 error errno 1
27 error [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
27 error Exit status 1
28 error Failed at the [email protected] start script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]
 andrespontt@Andress-MBP  ~/github/react-slingshot 

andrespontt · 2017-08-06T14:17:16Z

@DaneTheory I've implemented 6c54e55 changes and the error is fixed. Thanks!!!

DaneTheory · 2017-08-06T14:37:49Z

@coryhouse thought you merged jest-cli as a devDep which provided the fix? @andrespontt it's more of a monkey patch than a real fix. Cory mentioned those dashes that get removed play a significant role for other scripts to run properly down the line.

andrespontt · 2017-08-06T15:10:10Z

@DaneTheory understood. Let me know if you want me to test anything else. At least is starting, running the tests and displaying the react app in the browser.

This is the output after implement the file changes

added 1517 packages in 21.372s
 andrespontt@Andress-MBP  ~/github/react-slingshot   master ● 
 npm start

> [email protected] prestart /Users/andrespontt/github/react-slingshot
> npm-run-all --parallel start-message


> [email protected] start-message /Users/andrespontt/github/react-slingshot
> babel-node tools/startMessage.js

Starting app in dev mode...

> [email protected] start /Users/andrespontt/github/react-slingshot
> npm-run-all --parallel test:watch open:src lint:watch


> [email protected] test:watch /Users/andrespontt/github/react-slingshot
> npm run test --watch


> [email protected] open:src /Users/andrespontt/github/react-slingshot
> babel-node tools/srcServer.js


> [email protected] lint:watch /Users/andrespontt/github/react-slingshot
> npm run lint --watch


> [email protected] lint /Users/andrespontt/github/react-slingshot
> esw webpack.config.* src tools --color


> [email protected] test /Users/andrespontt/github/react-slingshot
> jest


 RUNS  src/components/FuelSavingsForm.spec.js
 RUNS  src/store/store.spec.js
 RUNS  src/utils/fuelSavingsCalculator.spec.js
 RUNS  src/components/FuelSavingsForm.spec.js
 RUNS  src/store/store.spec.js
 RUNS  src/utils/fuelSavingsCalculator.spec.js

Test Suites: 0 of 12 total
Tests:       0 total
Snapshots:   0 total
Time:        1s[BS] Access URLs:
 --------------------------------------
 PASS  src/store/store.spec.js:3000

 PASS  src/components/FuelSavingsForm.spec.js
 PASS  src/utils/fuelSavingsCalculator.spec.js
 PASS  src/reducers/fuelSavingsReducer.spec.js
 PASS  src/utils/mathHelper.spec.js
 PASS  src/utils/numberFormatter.spec.js

 RUNS  src/components/FuelSavingsResults.spec.js
 PASS  src/actions/fuelSavingsActions.spec.js
 PASS  src/components/FuelSavingsResults.spec.js
 PASS  src/utils/dateHelper.spec.js
 PASS  src/components/FuelSavingsTextInput.spec.js
 PASS  src/components/AboutPage.spec.js
 PASS  src/containers/FuelSavingsPage.spec.js

Test Suites: 12 passed, 12 total
Tests:       56 passed, 56 total
Snapshots:   1 passed, 1 total
Time:        5.35s
Ran all test suites.
webpack built 998c508679af20e14510 in 7227ms
  [25] (webpack)/buildin/module.js 517 bytes {0} [built]
  [27] ./node_modules/react-router/es/index.js 1.46 kB {0} [built]
 [199] multi ./src/webpack-public-path react-hot-loader/patch webpack-hot-middleware/client?reload=true ./src/index.js 64 bytes {0} [built]
 [200] ./src/webpack-public-path.js 612 bytes {0} [built]
 [201] ./node_modules/react-hot-loader/patch.js 41 bytes {0} [built]
 [202] ./node_modules/react-hot-loader/lib/patch.js 209 bytes {0} [built]
 [317] (webpack)-hot-middleware/client.js?reload=true 6.68 kB {0} [built]
 [318] ./node_modules/querystring-es3/index.js 127 bytes {0} [built]
 [321] ./node_modules/strip-ansi/index.js 161 bytes {0} [built]
 [323] (webpack)-hot-middleware/client-overlay.js 1.82 kB {0} [built]
 [328] (webpack)-hot-middleware/process-update.js 3.88 kB {0} [built]
 [329] ./src/index.js 1.65 kB {0} [built]
 [493] ./src/store/configureStore.js 2.2 kB {0} [built]
 [504] ./src/styles/styles.scss 1.34 kB {0} [built]
 [505] ./src/favicon.ico 57 bytes {0} [built]
    + 491 hidden modules
Child html-webpack-plugin for "index.html":
       [0] ./node_modules/html-webpack-plugin/lib/loader.js!./src/index.ejs 1.94 kB {0} [built]
       [1] ./node_modules/lodash/lodash.js 540 kB {0} [built]
       [2] (webpack)/buildin/global.js 509 bytes {0} [built]
       [3] (webpack)/buildin/module.js 517 bytes {0} [built]
webpack: Compiled successfully.

@coryhouse

* Issue #449 fix Issue 1: Removed extra dashes located in the package.json test scripts that cause start script to fail. Issue 2: Removed escape characters found in setupPrompts.js which cause linting to fail, thus breaking start script. * Jest fix Re-added previously removed dashes from test scripts in package.json that caused start script to fail. Instead, @coryhouse added in jest-cli as a dev-dep which resolves the issue.

@oshalygin

* removed react-router form package.json & installed react-router-dom. * completed index.src refactor. * re-implemented App.js * added notes to import changes & App.js * modified middleware array @ store/configureStore.js * updated yarn.lock file with fresh `yarn` command. * updated master branch. * upgraded react-hot-reloader to @3.0.0-beta.6 * removed extra "document.getElementById(app) from Root.js * moved react-router-redux to regular "dependencies" from "dev-dependencies" * cleaned Root.propTypes. * cleaned Root.js & App.js per @oshalygin feedback. * replaced .gitignore comment. * removed react-router form package.json & installed react-router-dom. * completed index.src refactor. * re-implemented App.js * added notes to import changes & App.js * Update FAQ.md fixed header on FAQ page * Update README.md fixed a few headers improperly declared * modified middleware array @ store/configureStore.js * Add react hot loader 3 (#392) - This commit wires up react-hot-loader 3 to be used in the application. There are numerous benefits to the latest release, all of which can be seen at https://github.com/gaearon/react-hot-loader - Note that the specific implementation around wrapping in a Root component is part of how react-hot-loader 3 needs to be configured. - Note that the package is brought in as a dependency, not a dev dependency because of how it is switched at runtime or not. - More information on the migration can be viewed at: https://github.com/gaearon/react-hot-loader/tree/master/docs\#migration-to-30 Related: #216 * Updated react-hot-loader to correct package version. (#401) * Add item to check if issues * updated yarn.lock file with fresh `yarn` command. * Fix formatting (#403) * updated master branch. * upgraded react-hot-reloader to @3.0.0-beta.6 * removed extra "document.getElementById(app) from Root.js * moved react-router-redux to regular "dependencies" from "dev-dependencies" * cleaned Root.js & App.js per @oshalygin feedback. * replaced .gitignore comment. * clean index.js * Add CONTRIBUTE.md (#431) * Add * Updated yarn lock using upgrade * Rename * Update * Upgrade to webpack 3 * Update yarn lock * Update snapshot * Set prod env when analyzing bundle * Add jest-cli as dependency * Revert PR #450 (#451) Removed change that removed additional dashes in npm test scripts in favor of adding jest-cli as a devDep. This commit instead focusses on issue 2 from #449 where setupPrompts.js had a bug that caused start script to fail. * Issue #449 fix (#450) * Issue #449 fix Issue 1: Removed extra dashes located in the package.json test scripts that cause start script to fail. Issue 2: Removed escape characters found in setupPrompts.js which cause linting to fail, thus breaking start script. * Jest fix Re-added previously removed dashes from test scripts in package.json that caused start script to fail. Instead, @coryhouse added in jest-cli as a dev-dep which resolves the issue. * Enhance babel env config to transpile for IE9+ (#452) * Fix for jest handling of static assets when running tests. See: (#457) jestjs/jest#2663 (comment) * Added tips for npm run lint and build errors (#151) (#460) * pushing changes from upstream fetch. * updated from rebase. * modified package versions in package.json & created new build. * update package.json * fixed conflicts with upstream master. * cleaned up PropTypes validations - react-router-redux throwing PropTypes error. * comment spell check & de-console on Root.js

caitlindev · 2017-09-03T23:43:27Z

@coryhouse @DaneTheory I'm sorry, but I'm still getting this error after installing watchman both via brew and npm. I'm able to run it by removing test:watch from the start script, but I want to get it working. Any ideas what my problem might be?

coryhouse · 2017-09-04T15:08:37Z

@caitlindev - Please share info about your env:

Node version
npm version
Operating System
Command line used
Steps to reproduce
Error Output

caitlindev · 2017-09-05T05:48:48Z

@coryhouse thanks for the quick response. Here are my specs:
node: v6.9.4
npm: v3.10.10
OS: macOS Sierra v10.12.2 (skimmed an article that this OS might be a problem, but didn't see any new tips beyond installing watchman)
command line: Terminal
Steps to reproduce:

clone repo
npm run setup
npm start
(btw, running the setup script, there's a prerelease version of react-router-redux in package.json)
-- OR --
clone repo
npm install
npm start

Error:

2017-09-05 00:44 node[68587] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-09-05 00:44 node[68587] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
      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:1406:11)

kwelch · 2017-10-02T01:07:21Z

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.

joel-regen · 2017-11-21T20:41:53Z

had similar issues, tried installing watchman with npm, failed. uninstalled it. installed it using brew. worked. thanks.

kwelch · 2017-11-21T20:49:39Z

Closing as it appears installing watchman resolves this issue for the remaining cases.

To install watchman run the following command to install using homebrew
brew install watchman

Alternatively, you can disable watchmen on jest calls by adding the --no-watchman flag.

axhamre · 2017-11-29T18:55:31Z

Can confirm that brew install watchman solved it for me as well.

Wouldn't it be a good idea to include that step to the installation guide?

nickytonline · 2017-11-29T20:50:02Z

@hundsim, great idea. Would you be willing to put up a PR to update the installation guide?

KashifAliChandio · 2017-12-12T18:54:48Z

I have install the following cmd
npm install -g create-react-app
create-react-app .

npm install --save react-router

and then i am starting dev server by using cmd

npm start

but i am facing an Error this type

D:\react\routes>npm start

[email protected] start D:\react\routes
react-scripts start

'react-scripts' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\kashif\AppData\Roaming\npm-cache_logs\2017-12-12T18_47_37
_524Z-debug.log

nickytonline · 2017-12-12T19:05:05Z

@KashifAliChandio, there is no need to install create-react-app and create a React app with it if you are using the react-slingshot starter kit for React/Redux. As well, there is no need to install react-router. It is part of the react-slingshot starter kit. Just follow the instructions in the README.md

Adds fix for the following issue after an initial `npm start -s` coryhouse#449

walreyes · 2018-01-31T20:43:48Z

Hey @nickytonline I've created a PR to add this fix to README. It'd be great to have it there so there is no need to dig to find the solution.

I just have a question: Is this only failing on Mac OS? If not, is there a fix for other platform that should be added?

We could continute the discussion over here: #536

Adds fix for the following issue after an initial `npm start -s` #449

coryhouse · 2018-01-31T21:07:37Z

This is a Mac only issue. Thanks for the PR! 👍

sonaskyla12 · 2018-06-21T19:35:20Z

hi please help me this error solution

my server was not running and was showing this pmblm "C:\Users\shubhendu\AppData\Roaming\npm-cache_logs\2018-06-21T19_02_48_535Z-debug.log"
various method tired by me was
1.installing the previous version of npm
2.since i don't have any folder of Roaming after appdata..so what shud i do now please helpme

muhyidin3222 · 2019-03-13T00:15:16Z

try paste this code in your terminal

sudo sysctl -w fs.inotify.max_user_instances=1024
sudo sysctl -w fs.inotify.max_user_watches=12288

ScottW1731 · 2019-03-15T17:06:08Z

So I and a friend are both on Windows PC and installing watchman did not work for us, we are on the liveSite Branch of this Repo
https://github.com/ScottW1731/Project3

we have followed every step that has been listed above, deleting repo and re-cloning, installing watchman, etc. none of us are getting the error, only him.

we have a mongoDB server running as our database for our APP and it must be running to run the app in the browser. so you will need a mongoDB in order to duplicate, as well as a dot env with a
JWT_secret=somethinghere

and then he npm starts,
and gets this error.

'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:dev: NODE_ENV=development concurrently "nodemon --ignore 'client/*'" "npm run client"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start:dev 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! C:\Users\46764740\AppData\Roaming\npm-cache_logs\2019-03-15T14_59_28_229Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: if-env NODE_ENV=production && npm run start:prod || npm run start:dev
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! C:\Users\46764740\AppData\Roaming\npm-cache_logs\2019-03-15T14_59_28_355Z-debug.log

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

mizanurrahman13 · 2020-06-01T10:30:31Z

ANYBODY PLEASE HELP ME WITH THIS ERROR

[email protected] start G:\VideoTutorial\GraphQL\graphql\examples\wrap-rest-api

npm-run-all --parallel start:rest start:graphql

[email protected] prestart:rest G:\VideoTutorial\GraphQL\graphql\examples\wrap-rest-api
node scripts/generate-db.js

[email protected] start:graphql G:\VideoTutorial\GraphQL\graphql\examples\wrap-rest-api
nodemon src/index.js

[nodemon] 1.18.11
[nodemon] to restart at any time, enter rs
[nodemon] watching: .
[nodemon] starting node src/index.js
internal/fs/utils.js:230
throw err;
^

Error: ENOENT: no such file or directory, mkdir
at Object.mkdirSync (fs.js:841:3)
at writeData (G:\VideoTutorial\GraphQL\graphql\examples\wrap-rest-api\scripts\generate-db.js:15:8)
at Object. (G:\VideoTutorial\GraphQL\graphql\examples\wrap-rest-api\scripts\generate-db.js:80:1)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
at internal/main/run_main_module.js:18:47 {
errno: -4058,
syscall: 'mkdir',
code: 'ENOENT'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] prestart:rest: node scripts/generate-db.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] prestart:rest script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Server running at http://localhost:5000

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\mizan\AppData\Roaming\npm-cache_logs\2020-06-01T08_12_51_952Z-debug.log
ERROR: "start:rest" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: npm-run-all --parallel start:rest start:graphql
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! C:\Users\mizan\AppData\Roaming\npm-cache_logs\2020-06-01T08_12_52_487Z-debug.log

p378 · 2020-07-24T12:41:42Z

Having problems Working wiht React when I run create-react-app command !!!!

20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: react-scripts start
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.

Walter-Paiva · 2021-08-30T19:34:34Z

LINUX
lsof -i tcp:3000
kill -9 {PID}

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

DaneTheory mentioned this issue Jul 18, 2017

Issue #449 fix #450

Merged

DaneTheory mentioned this issue Jul 18, 2017

Revert PR #450 #451

Merged

kwelch mentioned this issue Sep 1, 2017

Error on app start nashdev/jobs#34

Closed

techmexdev mentioned this issue Oct 26, 2017

Update package.json #496

Closed

kwelch closed this as completed Nov 21, 2017

nickytonline mentioned this issue Dec 29, 2017

error watching file exception, preventing npm start from working + fix #520

Closed

walreyes added a commit to walreyes/react-slingshot that referenced this issue Jan 31, 2018

Adds brew install watchman troubleshooting tip.

250a03c

Adds fix for the following issue after an initial `npm start -s` coryhouse#449

walreyes mentioned this issue Jan 31, 2018

Adds brew install watchman troubleshooting tip to README #536

Merged

coryhouse pushed a commit that referenced this issue Jan 31, 2018

Adds brew install watchman troubleshooting tip. (#536)

da8f544

Adds fix for the following issue after an initial `npm start -s` #449

rigobauer mentioned this issue Feb 2, 2018

[npm run test:e2e:run] CypressError: Timed out retrying: expected 'http://localhost:8001/login' to equal 'http://localhost:8001/' kentcdodds/testing-workshop#54

Closed

newsum2019 added a commit to newsum2019/singleshot that referenced this issue Oct 6, 2019

Adds brew install watchman troubleshooting tip. (#536)

adf264d

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

AMagicHarry added a commit to AMagicHarry/react-slingshot that referenced this issue Mar 11, 2024

Adds brew install watchman troubleshooting tip. (#536)

4d839ac

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

vincentowler pushed a commit to vincentowler/react-slingshot that referenced this issue May 24, 2024

Adds brew install watchman troubleshooting tip. (#536)

b3cbaad

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

gentle-breeze49 pushed a commit to gentle-breeze49/react-slingshot that referenced this issue Jul 23, 2024

Adds brew install watchman troubleshooting tip. (#536)

e2909e4

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

wleng0808 added a commit to wleng0808/react-slingshot that referenced this issue Mar 2, 2025

Adds brew install watchman troubleshooting tip. (#536)

eaf632c

Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449

Start script fails after initial installation. #449

Start script fails after initial installation. #449

Comments

DaneTheory commented Jul 18, 2017

DaneTheory commented Jul 18, 2017

coryhouse commented Jul 18, 2017

DaneTheory commented Jul 18, 2017

alexmattorr commented Jul 19, 2017

kwelch commented Jul 19, 2017

jonasfrid commented Jul 22, 2017 • edited Loading

coryhouse commented Jul 23, 2017

jonasfrid commented Jul 24, 2017 via email

DaneTheory commented Jul 24, 2017

andrespontt commented Aug 5, 2017 • edited Loading

nickytonline commented Aug 6, 2017

kwelch commented Aug 6, 2017 • edited Loading

DaneTheory commented Aug 6, 2017

DaneTheory commented Aug 6, 2017

andrespontt commented Aug 6, 2017 • edited Loading

DaneTheory commented Aug 6, 2017

andrespontt commented Aug 6, 2017 • edited Loading

andrespontt commented Aug 6, 2017 • edited Loading

DaneTheory commented Aug 6, 2017

andrespontt commented Aug 6, 2017

caitlindev commented Sep 3, 2017

coryhouse commented Sep 4, 2017

caitlindev commented Sep 5, 2017

kwelch commented Oct 2, 2017 • edited Loading

joel-regen commented Nov 21, 2017

kwelch commented Nov 21, 2017

axhamre commented Nov 29, 2017

nickytonline commented Nov 29, 2017

KashifAliChandio commented Dec 12, 2017

nickytonline commented Dec 12, 2017

walreyes commented Jan 31, 2018

coryhouse commented Jan 31, 2018

sonaskyla12 commented Jun 21, 2018

muhyidin3222 commented Mar 13, 2019

ScottW1731 commented Mar 15, 2019

mizanurrahman13 commented Jun 1, 2020 • edited Loading

p378 commented Jul 24, 2020

Walter-Paiva commented Aug 30, 2021

jonasfrid commented Jul 22, 2017 •

edited

Loading

andrespontt commented Aug 5, 2017 •

edited

Loading

kwelch commented Aug 6, 2017 •

edited

Loading

andrespontt commented Aug 6, 2017 •

edited

Loading

andrespontt commented Aug 6, 2017 •

edited

Loading

andrespontt commented Aug 6, 2017 •

edited

Loading

kwelch commented Oct 2, 2017 •

edited

Loading

mizanurrahman13 commented Jun 1, 2020 •

edited

Loading