node npm run watch Exit status 3221225725

npm err! code elifecycle
npm err code elifecycle npm err errno 9009
npm err exit status 2
npm err code elifecycle npm err errno 100
error code elifecycle npm run build
npm err code elifecycle npm err errno 139
code elifecycle exit status 1
npm err code elifecycle webpack

I had to format my drive and one of my projects is not working anymore. All the other same type of projects are working fine. It's Laravel + Vue JS. The problem is I cannot run npm run watch/dev or prodution. All of them are giving errors. Laravel 5.7 npm ver 6.4.1 node ver 10.15.0 windows 10

I've installed/uninstalled different node versions, no dice. I've deleted/install node modules again numerous time, nothing.

the error I'm getting, with npm run watch

@ watch C:\wamp64\www\projects\project.local npm run development -- --watch

@ development C:\wamp64\www\projects\project.local cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js "--watch"

npm ERR! code ELIFECYCLE npm ERR! errno 3221225725 npm ERR! @ development: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js "--watch" npm ERR! Exit status 3221225725 npm ERR! npm ERR! Failed at the @ development 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\Anthony\AppData\Roaming\npm-cache_logs\2019-01-14T07_07_30_914Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 3221225725 npm ERR! @ watch: npm run development -- --watch npm ERR! Exit status 3221225725 npm ERR! npm ERR! Failed at the @ 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! C:\Users\Anthony\AppData\Roaming\npm-cache_logs\2019-01-14T07_07_31_435Z-debug.log
the error I'm getting, with npm run production

@ production C:\wamp64\www\projects\project.local cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

npm ERR! code ELIFECYCLE npm ERR! errno 3221225725 npm ERR! @ production: cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js npm ERR! Exit status 3221225725 npm ERR! npm ERR! Failed at the @ production 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\Anthony\AppData\Roaming\npm-cache_logs\2019-01-14T07_08_21_587Z-debug.log
this is the log file

0 info it worked if it ends with ok 1 verbose cli [ 'C:\Program Files\nodejs\node.exe', 1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'production' ] 2 info using npm@6.4.1 3 info using node@v10.15.0 4 verbose run-script [ 'preproduction', 'production', 'postproduction' ] 5 info lifecycle @~preproduction: @ 6 info lifecycle @~production: @ 7 verbose lifecycle @~production: unsafe-perm in lifecycle true 8 verbose lifecycle @~production: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\wamp64\www\projects\project.local\node_modules.bin;C:\CMDER\bin;C:\CMDER\vendor\conemu-maximus5\ConEmu\Scripts;C:\CMDER\vendor\conemu-maximus5;C:\CMDER\vendor\conemu-maximus5\ConEmu;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\ProgramData\ComposerSetup\bin;C:\Program Files\PuTTY\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\wamp64\bin\php\php7.2.14;C:\Program Files\nodejs\;C:\Users\Anthony\AppData\Local\Microsoft\WindowsApps;C:\Users\Anthony\AppData\Roaming\Composer\vendor\bin;C:\Users\Anthony\AppData\Roaming\npm;C:\Program Files\Git\mingw64;C:\Program Files\Git\usr\bin;C:\CMDER 9 verbose lifecycle @~production: CWD: C:\wamp64\www\projects\project.local 10 silly lifecycle @~production: Args: [ '/d /s /c', 10 silly lifecycle 'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js' ] 11 silly lifecycle @~production: Returned: code: 3221225725 signal: null 12 info lifecycle @~production: Failed to exec production script 13 verbose stack Error: @ production: cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js 13 verbose stack Exit status 3221225725 13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16) 13 verbose stack at EventEmitter.emit (events.js:182:13) 13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:182:13) 13 verbose stack at maybeClose (internal/child_process.js:962:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5) 14 verbose pkgid @ 15 verbose cwd C:\wamp64\www\projects\project.local 16 verbose Windows_NT 10.0.17763 17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "production" 18 verbose node v10.15.0 19 verbose npm v6.4.1 20 error code ELIFECYCLE 21 error errno 3221225725 22 error @ production: cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js 22 error Exit status 3221225725 23 error Failed at the @ production script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 3221225725, true ]


This could be related to invalid .env file, if issues happen during parsing then such strange things can happen. Check if all MIX_ parameters are correct and ${} values are resolved. Pay attention to things like that.

PUSHER_APP_KEY=123
MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"

node npm run watch Exit status 3221225725 - node.js - html, watch: npm run development -- --watch npm ERR! Exit status 3221225725 npm ERR! npm ERR! Failed at the # watch script. npm ERR! This is probably not a  Noone has been able to reproduce Exit status 3221225725. As for your codepen I see the same output as Ruby Sass when testing with https://www.sassmeister.com/ This comment has been minimized.


Ok, this cost me about 2 hours, as there is no other useful output when running npm run build, other than react-scripts build fails with exit code 3221225725.

Fixing my .env files was the solution.

npm run dev: Exit status 3221225725 · Issue #5530 · nuxt/nuxt.js , npm run dev: Exit status 3221225725 #5530 conjuction with some other packages like stylelint or node-sass running on windows machines. Exit code 3221225477 is C0000005 or ACCESS_VIOLATION. This is probably some environmental issue but I think it should be tracked down in a matter similar to #8751 we've had before. This was referenced on Jan 4, 2016 Exit status 3221225477 returned from node scripts/build.js / Windows XP sass/node-sass#1326


npm install laravel-mix@^4.0.0 --save-dev

Research the version you were using before or which you should use

Exit Code 3221225725, when looking at the issue on github it said , npm start "start": "nodemon --exec npm run babel-node src/server.js" errno 1 22 error server@2.4.0 babel-node: `babel-node "src/server.js"` 22 error Exit status 1 23 error Failed at the server@2.4.0 babel-node script. youtube.com/watch? Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question.Provide details and share your research! But avoid …. Asking for help, clarification, or responding to other answers.


I cannot run server “npm ERR! Code ELIFECYCLE npm ERR! Errno , Failed at the step-00-practice@0.1.0 start script. npm ERR! 'run', 'build' ] 2 info using npm@5.8.0 3 info using node@v6.10.3 4 verbose run-script build: <code​>react-scripts build</code> 13 verbose stack Exit status 1 13  node npm run watch Exit status 3221225725. Hot Network Questions If an astronaut needs to go to the toilet during launch, what can/need they do?


npm ERR! code ELIFECYCLE on Terminal, Exit status 3221225725 npm ERR! npm ERR! watch: `npm run development -- --watch` npm ERR! '--watch' 1 verbose cli ] 2 info using > npm@6.14.4 3 info using node@v12.16.1 4 verbose run-script [ > 'predevelopment',  17941 error Exit status 3221225477 17942 error Failed at the node-sass@3.4.2 postinstall script 'node scripts/build.js'. 17942 error This is most likely a problem with the node-sass package, 17942 error not with npm itself.


npm run watch not compiling when data is off The 2019 Stack , April 2019 and salary with experienceLaravel 5.4 mix npm run dev 18node npm run watch Exit status 3221225725Can't run watch with I am working with laravel and as well using a lot of node packages for development. Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.