-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start script fails after initial installation. #449
Comments
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.
Fix provided in PR |
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! 👍 |
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.
Hey @DaneTheory and @coryhouse myself and another developer were receiving this error as well. We found out that |
The conversation about |
@DaneTheory may I ask how you fixed issue #1 above? I'm stuck with the same issue. npm version: Operating system:
|
@jonasfrid - Did you install watchman as described in this thread?
|
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
|
@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. |
just cloned and after setup & run and I got the same error. |
@andrespontt, what version of Node are you running? Can you also just paste the full error log you got? Thanks. |
@nickytonline We may want to set our |
@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. |
@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 |
@DaneTheory @nickytonline
System Operating &Hardware Overview:
Command line used
Error output
|
@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 I'll take a look at the log output. While I'm doing that, have you tried reproducing my fix for this mentioned here: Code diff found here: Let me know what you end up with. Thanks. We'll figure this out. |
@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
|
@DaneTheory I've implemented 6c54e55 changes and the error is fixed. Thanks!!! |
@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. |
@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
|
* 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.
* 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
@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? |
@caitlindev - Please share info about your env: Node version |
@coryhouse thanks for the quick response. Here are my specs:
Error:
|
For those still having this issue I recently, setup a new laptop with https://gist.github.com/kwelch/618a156d9aa7e1702f6b3cd2e6abc5b2 The believe I ran across the same issue as others in this thread and installing watchman fixed the issue completely. |
had similar issues, tried installing watchman with npm, failed. uninstalled it. installed it using brew. worked. thanks. |
Closing as it appears installing To install Alternatively, you can disable |
Can confirm that Wouldn't it be a good idea to include that step to the installation guide? |
@hundsim, great idea. Would you be willing to put up a PR to update the installation guide? |
I have install the following cmd 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
'react-scripts' is not recognized as an internal or external command, npm ERR! A complete log of this run can be found in: |
@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
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
This is a Mac only issue. Thanks for the PR! 👍 |
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" |
try paste this code in your terminal
|
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 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 and then he npm starts, 'NODE_ENV' is not recognized as an internal or external command, npm ERR! A complete log of this run can be npm ERR! A complete log of this run can be |
Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449
ANYBODY PLEASE HELP ME WITH THIS ERROR wrap-rest-api@1.0.0 start G:\VideoTutorial\GraphQL\graphql\examples\wrap-rest-api
[nodemon] 1.18.11 Error: ENOENT: no such file or directory, mkdir npm ERR! A complete log of this run can be found in: npm ERR! A complete log of this run can be found in: |
Having problems Working wiht React when I run create-react-app command !!!! 20 error code ELIFECYCLE |
LINUX |
Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449
Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449
Adds fix for the following issue after an initial `npm start -s` coryhouse/react-slingshot#449
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
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
ornpm install
, start script fails. Error output provided below.Error Output:
Issue 2:
After fixing issue 1 (see above), start script fails. Error output provided below.
Error Output:
The text was updated successfully, but these errors were encountered: