Error Command failed with exit code 1. On Windows 10 When run " yarn start " any idea?

[dukenst2006]

λ yarn start
yarn start v0.18.1
$ webpack-dashboard -c magenta -t 'Vue.js Starter Template' -- webpack-dev-server --config webpack/development.js --progress
Error: spawn Starter ENOENT
at notFoundError (C:\Users\Dukens\Documents\projects\vue\node_modules\webpack-dashboard\node_modules\cross-spawn\lib\enoent.js:11:11)
at verifyENOENT (C:\Users\Dukens\Documents\projects\vue\node_modules\webpack-dashboard\node_modules\cross-spawn\lib\enoent.js:46:16)
at ChildProcess.cp.emit (C:\Users\Dukens\Documents\projects\vue\node_modules\webpack-dashboard\node_modules\cross-spawn\lib\enoent.js:33:19)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
internal/process.js:172
throw errnoException(err, 'kill');
^

Error: kill ESRCH
at exports._errnoException (util.js:1036:11)
at process.kill (internal/process.js:172:13)
at process. (C:\Users\Dukens\Documents\projects\vue\node_modules\webpack-dashboard\bin\webpack-dashboard.js:70:11)
at emitOne (events.js:101:20)
at process.emit (events.js:188:7)
at process.exit (internal/process.js:146:15)
at Immediate. (C:\Users\Dukens\Documents\projects\vue\node_modules\blessed\lib\widgets\screen.js:221:15)
at runCallback (timers.js:574:20)
at tryOnImmediate (timers.js:554:5)
at processImmediate [as _immediateCallback] (timers.js:533:5)
error Command failed with exit code 1.

[villeristi]

Hmmm, try to run (from project root): rm -rf node_modules && yarn cache clean && yarn and after that try to run the start again.

[dukenst2006]

Thanks for answering @villeristi, unfortinately it's not work but when yarn fetch the packages, it give me those warnings ( fsevents compatible only with Mac OS, May be the problem is there ) :
warning fsevents@1.0.17: The platform "win32" is incompatible with this module.
info "fsevents@1.0.17" is an optional dependency and failed compatibility check. Excluding it from.
warning Incorrect peer dependency "eslint-plugin-import@^1.16.0".

[tmcmah1]

Unfortunately I'm getting the same thing with a freshly cloned repo. Using yarn 0.19.1 on Windows 7. I ran yarn cache clean followed by yarn, but still got the same errors when running yarn start:

yarn start v0.19.1
$ webpack-dashboard -c magenta -t 'Vue.js Starter Template' -- webpack-dev-server --config webpack/development.js --progress
Error: spawn Starter ENOENT
...

[wit3]

any solution ? 🐛

[tmcmah1]

I believe the problem might be that webpack-validator does not (and has no plans to) support Webpack v2.
js-dxtools/webpack-validator#105

I tried removing webpack-validator, but unfortunately was still not able to make this starter template work.

[villeristi]

Hi all, unfortunately haven't had any time digging in to this. But the error is not due to webpack-validator as it's not run on start and does not prevent the startup.

[dylinmaust]

Windows has an issue with the spawn command which is resolved using cross-spawn. Webpack-dashboard has a dependency on cross-spawn, and that's where the error is originating from (FormidableLabs/webpack-dashboard#83). I've tried updating webpack-dashboard to the latest, but it hasn't resolved the issue for me. My Node version is out of date too.. trying that next.

[dylinmaust]

You can currently work around the issue by not using webpack-dashboard, just replace yarn start command with webpack-dev-server --config webpack/development.js.

[ghost]

I was able to get it to work by removing the spaces from the -t parameter in the start script defined in package.json,
i.e.

"start": "webpack-dashboard -c magenta -t 'Vue.jsStarterTemplate' -- webpack-dev-server --config webpack/development.js --progress",

[baixiaomei]

error Command failed with exit code 1.

[villeristi]

Which command?
Which environment?
Which node-version?
The full error-msg?

[crathor]

yarn add webpack - solved this issue for me :)

[ereztdev]

I'm on win10, same issue, same error.
Everything was working fine, I got the error after installing a package for react (Formik).
I solved it with:
yarn cache clean
yarn
and then yarn start

[SageSanyue]

windows7 "yarn start" error, then I "yarn"(may it error also,but it doesnot matter), then "yarn start", it works!

[jakkoumodev]

@ereztdev
thank you
I solved it with:
yarn cache clean
yarn
and then yarn start

[Kaaviya-Nakkeeran]

Try
yarn
and yarn start

that will work

[tomsshow]

Hi! Working on a different project but I ran across a similar error in windows. What helped me was changing the single quote ' in the package.json script into a \".

for example: 'xyz' would become \"xyz\"

Hope it helps!

[ajayvarma1]

Hello guys ,

My operating system is Windows 10 .
I also face issue . Have any solution

Error :
==========================>

Command failed with exit code 1 (Unknown system error -1): yarnpkg

Error: Command failed with exit code 1 (Unknown system error -1): yarnpkg

• error.js:58 makeError
  [npm]/[gatsby-cli]/[execa]/lib/error.js:58:11

• index.js:112 handlePromise
  [npm]/[gatsby-cli]/[execa]/index.js:112:26

• next_tick.js:68 process._tickCallback
  internal/process/next_tick.js:68:7

[aramachandran7]

Hello guys ,
My operating system is Windows 10 .
I also face issue . Have any solution
Error :
==========================>
Command failed with exit code 1 (Unknown system error -1): yarnpkg
Error: Command failed with exit code 1 (Unknown system error -1): yarnpkg

error.js:58 makeError
[npm]/[gatsby-cli]/[execa]/lib/error.js:58:11

index.js:112 handlePromise
[npm]/[gatsby-cli]/[execa]/index.js:112:26

next_tick.js:68 process._tickCallback
internal/process/next_tick.js:68:7

Hey dude you don't have gatsby setup for windows properly -
try this.
worked for me.
https://www.gatsbyjs.org/docs/gatsby-on-windows/