Failed at `npm run dev` #714

ajhsu · 2018-01-09T09:51:18Z

For those people who encounter the following error messages:

$ vue init webpack-simple simple-example
$ cd simple-example
$ npm install
$ npm run dev

ajhsu-mbpr:simple-example ajhsu$ npm run dev

> simple-example@1.0.0 dev /Users/ajhsu/Git/vue/simple-example
> cross-env NODE_ENV=development webpack-dev-server --open --hot

webpack-dev-server 2.10.0
webpack 3.10.0
Usage: https://webpack.js.org/configuration/dev-server/

Config options:
  --config       Path to the config file
                         [string] [default: webpack.config.js or webpackfile.js]
  --config-name  Name of the config to use                              [string]

....

  --open-page   Open default browser with the specified page            [string]

Missing argument values: config, config-name, context, entry, module-bind, module-bind-post, module-bind-pre, output-path, output-filename, output-chunk-filename, output-source-map-filename, output-public-path, output-jsonp-function, output-library, output-library-target, records-input-path, records-output-path, records-path, define, target, watch-aggregate-timeout, devtool, resolve-alias, resolve-extensions, resolve-loader-alias, optimize-max-chunks, optimize-min-chunk-size, prefetch, provide, plugin, open-page
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! simple-example@1.0.0 dev: `cross-env NODE_ENV=development webpack-dev-server --open --hot`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the simple-example@1.0.0 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!     /Users/ajhsu/.npm/_logs/2018-01-09T09_28_10_300Z-debug.log

It seems caused by a known issue on webpack-dev-server@2.10.0. While the generated vue project is requiring webpack-dev-server@^2.9.1 which may install the broken version 2.10.0 that causes the error.

You can now temporary fix it by assigning the version of webpack-dev-server to 2.9.7 in your package.json like this: "webpack-dev-server": "2.9.7".

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

G-Veigar · 2018-01-09T09:58:07Z

+1

beer-on-ice · 2018-01-09T09:59:40Z

++++++11111111111111111111111111

roytime · 2018-01-09T10:00:09Z

yarn remove webpack-dev-server
yarn add webpack-dev-server@2.9.1 --dev
yarn run dev

OK!

axtho · 2018-01-09T10:06:34Z

Yeah, it is a webpack 2.9.10 issue. Downgrading this will help.

ajhsu · 2018-01-09T10:09:46Z

@axtho Actually there has no webpack-dev-server@2.9.10, it's the problem of webpack-dev-server@2.10.0. 😄

axtho · 2018-01-09T10:10:44Z

Right. That is correct.

qingyunmeng042515 · 2018-01-09T10:51:14Z

yarn remove webpack-dev-server
yarn add webpack-dev-server@2.9.1 --dev
yarn run dev

亲测可以

yyx990803 · 2018-01-09T22:54:06Z

2.10.1 should fix it too.

pvfhv · 2018-01-16T11:46:10Z

2.11.0无此Bug

rgalaxy · 2018-01-22T07:42:06Z

'cross-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! my-app@1.0.0 dev: cross-env NODE_ENV=development webpack-dev-server --open --hot
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@1.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

hi I still encounter this even after changing the webpack-dev-server to ^2.9.7

i just install vue-cli and this is my package json

{
"name": "my-app",
"description": "A Vue.js project",
"version": "1.0.0",
"author": "",
"license": "MIT",
"private": true,
"scripts": {
"dev": "cross-env NODE_ENV=development webpack-dev-server --open --hot",
"build": "cross-env NODE_ENV=production webpack --progress --hide-modules"
},
"dependencies": {
"vue": "^2.5.11"
},
"browserslist": [
"> 1%",
"last 2 versions",
"not ie <= 8"
],
"devDependencies": {
"babel-core": "^6.26.0",
"babel-loader": "^7.1.2",
"babel-preset-env": "^1.6.0",
"babel-preset-stage-3": "^6.24.1",
"cross-env": "^5.0.5",
"css-loader": "^0.28.7",
"file-loader": "^1.1.4",
"node-sass": "^4.5.3",
"sass-loader": "^6.0.6",
"vue-loader": "^13.0.5",
"vue-template-compiler": "^2.4.4",
"webpack": "^3.6.0",
"webpack-dev-server": "^2.9.7"
}
}

how do i fix this?

ajhsu · 2018-01-23T09:16:47Z

@rgalaxy That's not the problem related to this issue;

I think It's simply because you haven't run npm install before npm run dev or npm run build yet.

anson-GH · 2018-09-13T01:36:46Z

change the config >index.js port: 8080 to other port eg, port: 8081

slwzero · 2019-01-03T03:21:53Z

npm uninstall webpack-dev-server
npm install webpack-dev-server@2.9.1 --dev
npm run serve

It works perfectly!💝

tannhauserr · 2019-01-29T11:33:50Z

@slwzero thanks, in 2019 and it's still failing

MattHaydon · 2019-01-31T18:32:31Z

@slwzero thanks, in 2019 and it's still failing

Same. --unsafe-perm seemed. to fix.

automatonatm · 2019-02-11T14:58:38Z

npm remove webpack-dev-server
npm add webpack-dev-server@2.9.1 --dev
nmp run dev

this solves the whole problem

toeurtenh · 2019-03-24T10:07:42Z

thank you, it works for me

161710132 · 2019-03-31T14:51:59Z

help me

mohammadnazari110 · 2019-04-07T09:24:34Z

rm -rf node_modules
rm package-lock.json yarn.lock
npm cache clear --force
npm install

npm add webpack-dev-server@2.9.1 --dev

toeurtenh · 2019-04-15T08:36:07Z

thank you it works

…

On Sun, Apr 7, 2019 at 10:24 AM mohammad nazari ***@***.***> wrote: rm -rf node_modules rm package-lock.json yarn.lock npm cache clear --force npm install npm add ***@***.*** --dev — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#714 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIHb5FEHLCXEK19MhwzPamRu3E6DSHd_ks5vebldgaJpZM4RXkL_> .

vinnysihombing · 2019-08-08T07:44:39Z

okee ^^

uroosehar1 · 2020-06-17T07:35:03Z

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! hellovue@1.0.0 dev: webpack-dev-server --inline --progress --config build/webpack.dev.conf.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the hellovue@1.0.0 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! /Users/uroo/.npm/_logs/2020-06-17T07_32_00_033Z-debug.log

cannot run node project suddenly

FOWnglp · 2022-04-27T18:16:15Z

webpack-dev-server

我的还是不行

sarwaras · 2022-05-19T03:02:49Z

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! 03-webpack-ts@1.0.0 dev: cross-env NODE_ENV=development webpack-dev-server --config build/webpack.config.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the 03-webpack-ts@1.0.0 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\rtt\AppData\Roaming\npm-cache_logs\2022-05-19T02_56_16_701Z-debug.log
Waiting for the debugger to disconnect...

The above method still doesn't solve my problem~

yyx990803 closed this as completed Jan 9, 2018

vijaypandiyan mentioned this issue Nov 19, 2018

Error spawn EACCES with webpack dev server for vue-cli webpack/webpack-dev-server#940

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Failed at `npm run dev` #714

Failed at `npm run dev` #714

ajhsu commented Jan 9, 2018 •

edited

Loading

G-Veigar commented Jan 9, 2018

beer-on-ice commented Jan 9, 2018

roytime commented Jan 9, 2018

axtho commented Jan 9, 2018

ajhsu commented Jan 9, 2018 •

edited

Loading

axtho commented Jan 9, 2018

qingyunmeng042515 commented Jan 9, 2018

yyx990803 commented Jan 9, 2018

pvfhv commented Jan 16, 2018

rgalaxy commented Jan 22, 2018

ajhsu commented Jan 23, 2018 •

edited

Loading

anson-GH commented Sep 13, 2018

slwzero commented Jan 3, 2019 •

edited

Loading

tannhauserr commented Jan 29, 2019

MattHaydon commented Jan 31, 2019

automatonatm commented Feb 11, 2019

toeurtenh commented Mar 24, 2019 •

edited

Loading

161710132 commented Mar 31, 2019

mohammadnazari110 commented Apr 7, 2019

toeurtenh commented Apr 15, 2019 via email

vinnysihombing commented Aug 8, 2019

uroosehar1 commented Jun 17, 2020

FOWnglp commented Apr 27, 2022

sarwaras commented May 19, 2022

Failed at npm run dev #714

Failed at npm run dev #714

Comments

ajhsu commented Jan 9, 2018 • edited Loading

G-Veigar commented Jan 9, 2018

beer-on-ice commented Jan 9, 2018

roytime commented Jan 9, 2018

axtho commented Jan 9, 2018

ajhsu commented Jan 9, 2018 • edited Loading

axtho commented Jan 9, 2018

qingyunmeng042515 commented Jan 9, 2018

yyx990803 commented Jan 9, 2018

pvfhv commented Jan 16, 2018

rgalaxy commented Jan 22, 2018

ajhsu commented Jan 23, 2018 • edited Loading

anson-GH commented Sep 13, 2018

slwzero commented Jan 3, 2019 • edited Loading

tannhauserr commented Jan 29, 2019

MattHaydon commented Jan 31, 2019

automatonatm commented Feb 11, 2019

toeurtenh commented Mar 24, 2019 • edited Loading

161710132 commented Mar 31, 2019

mohammadnazari110 commented Apr 7, 2019

toeurtenh commented Apr 15, 2019 via email

vinnysihombing commented Aug 8, 2019

uroosehar1 commented Jun 17, 2020

FOWnglp commented Apr 27, 2022

sarwaras commented May 19, 2022

Failed at `npm run dev` #714

Failed at `npm run dev` #714

ajhsu commented Jan 9, 2018 •

edited

Loading

ajhsu commented Jan 9, 2018 •

edited

Loading

ajhsu commented Jan 23, 2018 •

edited

Loading

slwzero commented Jan 3, 2019 •

edited

Loading

toeurtenh commented Mar 24, 2019 •

edited

Loading