-
Notifications
You must be signed in to change notification settings - Fork 84
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
npm start failing #46
Comments
Hey @Pesinn, Were there any errors during genration of the project? |
Hey stylesuxx and thanks for fast response. I get this error after running yo generator-react-webpack-redux +-- UNMET PEER DEPENDENCY [email protected] Here is detailed error: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): |
so, did you install webpack as peer dep?
|
I've tried to install different versions of webpack, but none of them seems to work. I always get this error: `-- UNMET PEER DEPENDENCY [email protected] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): I thought it could be some problem with npm but then I installed another generator, that has webpack, without any problems. |
So
in your project root does not solve the problem? Do you use nvm? Maybe you could quickly switch to a newer node version and generate a fresh project. I use v6.6.0 for development. I just want to cross check, since I do not have windows I can not really test that case properly. |
I installed version v.6.6.0 but it doesn't make any difference. I get the same error. And npm install [email protected] isn't working either. I tried few beta versions, from 2.2 up to 2.5. I also tried to uninstall webpack and install it again, and webpack-dev-server also. But nothing works. |
Hmm, do you, by any chance have webpack installed globally? If so please remove it, so the project uses the locally installed webpack version. That's the only thing I can think of right now. I do not have a windows dev setup on which I could test, but can you please post output of
Maybe I can ask someone for help. |
Hi, i got the same problem. ` node -v && npm -v npm ERR! Linux 4.4.0-31-generic npm ERR! Please include the following file with any support request: ` I already install webpack and webpack-dev-server |
OK, I am getting this now too. |
Yay! Thank You! Installing [email protected] works fine on me. |
Hi. I get the same error as @Pesinn reports. Running |
Sorry for late response, but it works now when I install [email protected]. Thank you :) |
The following is my config with the latest webpack and webpack-dev-server which can work. "webpack": "2.1.0-beta.22",
"webpack-dev-server": "^2.1.0-beta.9" |
it looks like beta 23+ or so introduced config schema validation ... so first:
then |
@erfangc Thank you for this. Point is - this is part of the main generator and not this one, I am depending on the main generator and made the mistake to update my generator to the newest version of the base generator which is still in beta, and will be as long as webpack is... |
@stylesuxx Following your instructions worked for me, too ( |
@erfangc good to know the change of webpack 23+ 👍 |
Webpack is stable - this should no longer be an issue. Closing this down. |
I get this error when I do: npm start
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users...\npm\node_modules\npm\bin\npm-cli.js" "run" "dist"
npm ERR! node v4.5.0
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! [email protected] dist:
npm run clean && npm run copy && webpack --progress --bail --env dist -p
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] serve:dev script 'webpack-dev-server --open --env dev'.
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 react-webpack-redux package,
npm ERR! not with npm itself.
I have the latest node- and npm versions:
node version: v4.5.0
npm version: 3.10.8
The text was updated successfully, but these errors were encountered: