I am new to protractor and visual studio code so bare with me. I have already tried to look for solutions to this on stackoverflow and google but was not successful.
Basically I am running e2e tests through protractor inside visual studio code with a terminal command e.g. 'npm run e2e:local' which runs 'export ENVIRONMENT=local && protractor ./e2e/protractor.conf.js
The tests run fine and all except there is not any kind of stack trace upon failure, so I have no idea how/where to look for the error in my code.
Here is an example output of a test run:
[16:55:47] I/direct - Using ChromeDriver directly...
Jasmine started
Construction NZ Level 50 user
✗ Can create a project with all fields filled in and with a contractor
- Failed: Invalid locator
**************************************************
* Failures *
**************************************************
1) Construction NZ Level 50 user Can create a project with all fields filled in and with a contractor
- Failed: Invalid locator
Executed 1 of 3 specs (1 FAILED) (2 SKIPPED) in 31 secs.
[16:56:22] I/launcher - 0 instance(s) of WebDriver still running
[16:56:22] I/launcher - chromeANY #01 failed 1 test(s)
[16:56:22] I/launcher - overall: 1 failed spec(s)
[16:56:22] E/launcher - Process exited with error code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! HazardCoHub#1.3.10 e2e:local: `export ENVIRONMENT=local && protractor ./e2e/protractor.conf.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the HazardCoHub#1.3.10 e2e:local 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/dmitrikoudrin/.npm/_logs/2020-08-27T04_56_22_187Z-debug.log```
So as you can see it just says "Failed: Invalid locator" which is of no help to me as it could be any one of a 100 locators in the code.
All I want is for it give a standard stack trace and point me to the function that's failing. It would be even better if it could print what locator it tried to find/use before failing.
Full log:
0 info it worked if it ends with ok
1 verbose cli [ '/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/bin/node',
1 verbose cli '/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/bin/npm',
1 verbose cli 'run',
1 verbose cli 'e2e:local' ]
2 info using npm#6.9.0
3 info using node#v10.16.3
4 verbose run-script [ 'pree2e:local', 'e2e:local', 'poste2e:local' ]
5 info lifecycle HazardCoHub#1.3.11~pree2e:local: HazardCoHub#1.3.11
6 info lifecycle HazardCoHub#1.3.11~e2e:local: HazardCoHub#1.3.11
7 verbose lifecycle HazardCoHub#1.3.11~e2e:local: unsafe-perm in lifecycle true
8 verbose lifecycle HazardCoHub#1.3.11~e2e:local: PATH: /Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/dmitrikoudrin/hazardco_hub_2/node_modules/.bin:/Users/dmitrikoudrin/Library/Android/sdk/tools:/Users/dmitrikoudrin/Library/Android/sdk/build-tools:/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/dmitrikoudrin/Library/Android/sdk/tools:/Users/dmitrikoudrin/Library/Android/sdk/build-tools:/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/bin
9 verbose lifecycle HazardCoHub#1.3.11~e2e:local: CWD: /Users/dmitrikoudrin/hazardco_hub_2
10 silly lifecycle HazardCoHub#1.3.11~e2e:local: Args: [ '-c',
10 silly lifecycle 'export ENVIRONMENT=local && protractor ./e2e/protractor.conf.js' ]
11 silly lifecycle HazardCoHub#1.3.11~e2e:local: Returned: code: 1 signal: null
12 info lifecycle HazardCoHub#1.3.11~e2e:local: Failed to exec e2e:local script
13 verbose stack Error: HazardCoHub#1.3.11 e2e:local: `export ENVIRONMENT=local && protractor ./e2e/protractor.conf.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid HazardCoHub#1.3.11
15 verbose cwd /Users/dmitrikoudrin/hazardco_hub_2
16 verbose Darwin 19.6.0
17 verbose argv "/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/bin/node" "/Users/dmitrikoudrin/.nvm/versions/node/v10.16.3/bin/npm" "run" "e2e:local"
18 verbose node v10.16.3
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error HazardCoHub#1.3.11 e2e:local: `export ENVIRONMENT=local && protractor ./e2e/protractor.conf.js`
22 error Exit status 1
23 error Failed at the HazardCoHub#1.3.11 e2e:local script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Make sure your config has
jasmineNodeOpts: {
// If true, display spec names.
isVerbose: true,
// If true, print colors to the terminal.
showColors: true,
// If true, include stack traces in failures.
includeStackTrace: true,
},
Related
I have an error when I build my electron app npm run dist but I didn't found a solution that resolve it.
Command line defined: "COMPRESS=auto"
Command line defined: "BUILD_UNINSTALLER"
Command line defined: "UNINSTALLER_OUT_FILE=C:\laragon\www\app\dist\.__uninstaller-nsis-App_App.exe"
Processing config: C:\Users\User\AppData\Local\electron-builder\Cache\nsis\nsis-3.0.3.2\nsisconf.nsh
Processing script file: "<stdin>" (ACP)
Error output:
Plugin not found, cannot call UAC::_
Error in macro _UAC_MakeLL_Cmp on macroline 2
Error in macro _UAC_IsInnerInstance on macroline 1
Error in macro _If on macroline 9
Error in macro FUNCTION_INSTALL_MODE_PAGE_FUNCTION on macroline 2
Error in macro PAGE_INSTALL_MODE on macroline 17
!include: error in script: "assistedInstaller.nsh" on line 60
Error in script "<stdin>" on line 112 -- aborting creation process
at ChildProcess.<anonymous> (C:\laragon\www\app\node_modules\builder-util\src\util.ts:244:14)
at Object.onceWrapper (events.js:288:20)
at ChildProcess.emit (events.js:200:13)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! App_App#2.3.0 dist: `build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the App_App#2.3.0 dist 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\User\AppData\Roaming\npm-cache\_logs\2020-11-04T10_47_57_428Z-debug.log
The content of the log file:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\laragon2\\bin\\nodejs\\node-v12\\node.exe',
1 verbose cli 'C:\\laragon2\\bin\\nodejs\\node-v12\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dist'
1 verbose cli ]
2 info using npm#6.9.0
3 info using node#v12.5.0
4 verbose run-script [ 'predist', 'dist', 'postdist' ]
5 info lifecycle App_App#2.3.0~predist: App_App#2.3.0
6 info lifecycle App_App#2.3.0~dist: App_App#2.3.0
7 verbose lifecycle App_App#2.3.0~dist: unsafe-perm in lifecycle true
8 verbose lifecycle App_App#2.3.0~dist: PATH: C:\laragon2\bin\nodejs\node-v12\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;
9 verbose lifecycle App_App#2.3.0~dist: CWD: C:\laragon\www\app
10 silly lifecycle App_App#2.3.0~dist: Args: [ '/d /s /c', 'build' ]
11 silly lifecycle App_App#2.3.0~dist: Returned: code: 1 signal: null
12 info lifecycle App_App#2.3.0~dist: Failed to exec dist script
13 verbose stack Error: App_App#2.3.0 dist: `build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\laragon2\bin\nodejs\node-v12\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:200:13)
13 verbose stack at ChildProcess.<anonymous> (C:\laragon2\bin\nodejs\node-v12\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:200:13)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid App_App#2.3.0
15 verbose cwd C:\laragon\www\app
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\laragon2\\bin\\nodejs\\node-v12\\node.exe" "C:\\laragon2\\bin\\nodejs\\node-v12\\node_modules\\npm\\bin\\npm-cli.js" "run" "dist"
18 verbose node v12.5.0
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error App_App#2.3.0 dist: `build`
22 error Exit status 1
23 error Failed at the App_App#2.3.0 dist script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I tried to clean npm caches, remove all modules and reinstall it, delete electron-builder caches but nothing happened.
I tested to build the same project in other computer and it works fine.
Does anyone have a solution to my problem?
Thank in advance
If anyone has a similar error I have found the problem: it must not have unicode characters in the electron builder cache path. In my case it was my windows user session.
To change electron cache path:
export ELECTRON_BUILDER_CACHE=C:\Temp
And run npm run dist or yarn dist
Hope this answer can help someone in the future.
I installed node.js for the sake of sass compiling, i havent touched any of javascript for now so all the documentation I went through to solve this problem is really complicated for me. So when i put npm init -y command in VScode terminal it installs package.json file that has a debug property between line 5 and 6.
when i click on "debug" errors that show into my terminal are these...
"Error: no test specified"
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! c#1.0.0 test: `echo "Error: no test specified" && exit 1`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the c#1.0.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\AppData\Roaming\npm-cache\_logs\2020-09-27T00_42_32_091Z-debug.log
Waiting for the debugger to disconnect...
PS C:\Users\Desktop\c>
And here is log file
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'test'
1 verbose cli ]
2 info using npm#6.14.8
3 info using node#v14.11.0
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle c#1.0.0~pretest: c#1.0.0
6 info lifecycle c#1.0.0~test: c#1.0.0
7 verbose lifecycle c#1.0.0~test: unsafe-perm in lifecycle true
8 verbose lifecycle c#1.0.0~test: PATH: C:\Users\\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\\Desktop\c\node_modules\.bin;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\nodejs\;C:\Users\\AppData\Local\Microsoft\WindowsApps;C:\Users\\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\\AppData\Roaming\npm
9 verbose lifecycle c#1.0.0~test: CWD: C:\Users\\Desktop\c
10 silly lifecycle c#1.0.0~test: Args: [ '/d /s /c', 'echo "Error: no test specified" && exit 1' ]
11 silly lifecycle c#1.0.0~test: Returned: code: 1 signal: null
12 info lifecycle c#1.0.0~test: Failed to exec test script
13 verbose stack Error: c#1.0.0 test: `echo "Error: no test specified" && exit 1`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1047:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid c#1.0.0
15 verbose cwd C:\Users\\Desktop\c
16 verbose Windows_NT 10.0.19041
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "test"
18 verbose node v14.11.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error c#1.0.0 test: `echo "Error: no test specified" && exit 1`
22 error Exit status 1
23 error Failed at the c#1.0.0 test script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
VScode is giving you a quick way of running 'npm test', which is running exactly as expected. You can specify commands to run in the "scripts" property. As you can see, there is one for "test", which is outputting exactly what is written there. That is what 'debug' does. You need to hook a real test command there for debug to do anything useful.
That debug stuff is the output for a npm run test which you don't care about if you're only installing a package.json so you can install sass for development. If you want to be able to run tests via npm run test, change the value of the key/value pair on line 7 to run your tests.
"test": "someTestCommand.exe"
But again, if you're only doing this to get sass compiling, you can safely ignore it.
Please find the error logs which I am getting in the terminal
fruits-vegetables#0.1.0 start C:\Users\MY PC\My_Front_End\fruits-vegetables
> react-scripts start
Could not find a required file.
Name: index.html
Searched in: C:\Users\MY PC\My_Front_End\fruits-vegetables\public
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fruits-vegetables#0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fruits-vegetables#0.1.0 start 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\MY PC\AppData\Roaming\npm-cache\_logs\2019-12-20T15_57_41_927Z-debug.log
Please find the debug error log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\MY PC\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.13.4
3 info using node#v12.10.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle fruits-vegetables#0.1.0~prestart: fruits-vegetables#0.1.0
6 info lifecycle fruits-vegetables#0.1.0~start: fruits-vegetables#0.1.0
7 verbose lifecycle fruits-vegetables#0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle fruits-vegetables#0.1.0~start: PATH: C:\Users\MY PC\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\MY PC\My_Front_End\fruits-vegetables\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python27\;C:\Python27\Scripts;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Users\MY PC\AppData\Local\Microsoft\WindowsApps;C:\Users\MY PC\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\MY PC\AppData\Roaming\npm;C:\Program Files\Git\bin;C:\Program Files (x86)\Nmap
9 verbose lifecycle fruits-vegetables#0.1.0~start: CWD: C:\Users\MY PC\My_Front_End\fruits-vegetables
10 silly lifecycle fruits-vegetables#0.1.0~start: Args: [ '/d /s /c', 'react-scripts start' ]
11 silly lifecycle fruits-vegetables#0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle fruits-vegetables#0.1.0~start: Failed to exec start script
13 verbose stack Error: fruits-vegetables#0.1.0 start: `react-scripts start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\MY PC\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:209:13)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\MY PC\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:209:13)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid fruits-vegetables#0.1.0
15 verbose cwd C:\Users\MY PC\My_Front_End\fruits-vegetables
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\MY PC\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.10.0
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error fruits-vegetables#0.1.0 start: `react-scripts start`
22 error Exit status 1
23 error Failed at the fruits-vegetables#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Moreover, I have already tried these suggestions:
delete node modules and package-lock.json
then ran command: npm update
then ran command: npm install
and when I ran npm start I got the same error as above
One more thing which I noticed, whenever I freshly install a react app then I used to get App.js, index.js, index.html even a src folder, I am not getting all these. Please help!
I'm also faced this issue before but fortunately i fixed it for ever you can fix this by going to the ->control pannel ->system and security ->system-> advanced system settings ->environment variables look for system variables and look for ComSpec make sure the path is like this C:\Windows\system32\cmd.exe and restart the system and see it will work
When i run my react node project in my ubuntu system with command npm run dev, It gives me error log and it doesn't opening in my browser, even when i try to open it with localhost:3000 it doesn't working, here is my error log, can anyone please look in it and give me proper solution ?
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'client' ]
2 info using npm#3.5.2
3 info using node#v8.10.0
4 verbose run-script [ 'preclient', 'client', 'postclient' ]
5 info lifecycle mern-auth#1.0.0~preclient: mern-auth#1.0.0
6 silly lifecycle mern-auth#1.0.0~preclient: no script for preclient, continuing
7 info lifecycle mern-auth#1.0.0~client: mern-auth#1.0.0
8 verbose lifecycle mern-auth#1.0.0~client: unsafe-perm in lifecycle true
9 verbose lifecycle mern-auth#1.0.0~client: PATH: /usr/share/npm/bin/node-gyp-bin:/var/www/mern-plaid/node_modules/.bin:/usr/share/npm/bin/node-gyp-bin:/var/www/mern-plaid/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
10 verbose lifecycle mern-auth#1.0.0~client: CWD: /var/www/mern-plaid
11 silly lifecycle mern-auth#1.0.0~client: Args: [ '-c', 'npm start --prefix client' ]
12 silly lifecycle mern-auth#1.0.0~client: Returned: code: 1 signal: null
13 info lifecycle mern-auth#1.0.0~client: Failed to exec client script
14 verbose stack Error: mern-auth#1.0.0 client: `npm start --prefix client`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at EventEmitter.emit (events.js:214:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at ChildProcess.emit (events.js:214:7)
14 verbose stack at maybeClose (internal/child_process.js:925:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid mern-auth#1.0.0
16 verbose cwd /var/www/mern-plaid
17 error Linux 5.0.0-25-generic
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "client"
19 error node v8.10.0
20 error npm v3.5.2
21 error code ELIFECYCLE
22 error mern-auth#1.0.0 client: `npm start --prefix client`
22 error Exit status 1
23 error Failed at the mern-auth#1.0.0 client script 'npm start --prefix client'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the mern-auth package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error npm start --prefix client
23 error You can get information on how to open an issue for this project with:
23 error npm bugs mern-auth
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls mern-auth
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
This is the error in my console
npm ERR! code ELIFECYCLE
npm ERR! errno 3221225477
npm ERR! sedona#0.1.0 start: `npm run build && gulp serve`
npm ERR! Exit status 3221225477
npm ERR!
npm ERR! Failed at the sedona#0.1.0 start 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\User\AppData\Roaming\npm-cache\_logs\2017-07-21T19_40_30_516Z
-debug.log
This is the "debug.log" file from AppData/Roaming etc. path
0 info it worked if it ends with ok
1 verbose cli [ 'D:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#5.3.0
3 info using node#v8.2.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle sedona#0.1.0~prestart: sedona#0.1.0
6 info lifecycle sedona#0.1.0~start: sedona#0.1.0
7 verbose lifecycle sedona#0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle sedona#0.1.0~start: PATH: D:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\User\Desktop\user.github.io\node_modules\.bin;C:\Users\User\Desktop\cmder\bin;C:\Users\User\Desktop\cmder\vendor\git-for-windows\cmd;C:\Users\User\Desktop\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\Users\User\Desktop\cmder\vendor\conemu-maximus5;C:\Users\User\Desktop\cmder\vendor\conemu-maximus5\ConEmu;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Calibre2\;C:\Program Files (x86)\Skype\Phone\;D:\Program Files\nodejs\;C:\Users\User\AppData\Roaming\npm;C:\Users\User\Desktop\cmder\vendor\git-for-windows\usr\bin;C:\Users\User\Desktop\cmder\vendor\git-for-windows\usr\share\vim\vim74;C:\Users\User\Desktop\cmder\
9 verbose lifecycle sedona#0.1.0~start: CWD: C:\Users\User\Desktop\user.github.io
10 silly lifecycle sedona#0.1.0~start: Args: [ '/d /s /c', 'npm run build && gulp serve' ]
11 silly lifecycle sedona#0.1.0~start: Returned: code: 3221225477 signal: null
12 info lifecycle sedona#0.1.0~start: Failed to exec start script
13 verbose stack Error: sedona#0.1.0 start: `npm run build && gulp serve`
13 verbose stack Exit status 3221225477
13 verbose stack at EventEmitter.<anonymous> (D:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:289:16)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at EventEmitter.emit (events.js:213:7)
13 verbose stack at ChildProcess.<anonymous> (D:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at ChildProcess.emit (events.js:213:7)
13 verbose stack at maybeClose (internal/child_process.js:921:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid sedona#0.1.0
15 verbose cwd C:\Users\user\Desktop\user.github.io
16 verbose Windows_NT 6.1.7601
17 verbose argv "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v8.2.1
19 verbose npm v5.3.0
20 error code ELIFECYCLE
21 error errno 3221225477
22 error sedona#0.1.0 start: `npm run build && gulp serve`
22 error Exit status 3221225477
23 error Failed at the sedona#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225477, true ]
I have already downloaded another gulp-sass projects from other peolpe github's and replace it contains with my own html-sass-js-img files. Error still here btw.
I have already reinstall cmder and node.js. Twice. Error still here.
I have already delete "node-modules" folder from my project and made "npm i" command - nothing changed.
And one fun thing - files in folder "build" updated like always (if you manual lauch them in browser like in old times). But in root folder seems like gulp-sass just don't see that anything happen and zero changes displayed in localhost 3000.
My previous build from yesterday work fine (seemingly) and builds from another people from github work fine too, but why my new build with some changes make that crash??? Only cause sass files changed?
So, there's an interesting cause of this in Jest in VSCode while debugging with Node 12.4.0. When running jest and babel, and placing breakpoints in static classes, the second you place them in the static class, in a static method, node throws this error. To fix, dont write weird static classes.