I am running the following command (windows) (npm v7.0.0-beta.8) (node v12.18.1)
ng new light-webapp
It throws the following error
...
CREATE light-webapp/e2e/tsconfig.json (299 bytes)
CREATE light-webapp/e2e/src/app.e2e-spec.ts (645 bytes)
CREATE light-webapp/e2e/src/app.po.ts (301 bytes)
| Installing packages...npm ERR! code ERESOLVE
npm ERR! unable to resolve dependency tree
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\...\AppData\Local\npm-cache\_logs\2021-05-15T14_51_21_350Z-debug.log
× Package install failed, see above.
The Schematic workflow failed. See above.
The above mentioned error log shows the following:
...
1899 timing idealTree:node_modules/karma-jasmine Completed in 0ms
1900 silly placeDep jasmine-core#>=3.7.1 Symbol(CONFLICT) for: karma-jasmine-html-reporter#1.6.0
1901 timing idealTree Completed in 15783ms
1902 timing command:install Completed in 15789ms
1903 verbose type peer
1904 verbose stack Error: unable to resolve dependency tree
1904 verbose stack at Arborist.[placeDep] (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\arborist\build-ideal-tree.js:814:27)
1904 verbose stack at C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\arborist\build-ideal-tree.js:631:46
1904 verbose stack at Array.map (<anonymous>)
1904 verbose stack at Arborist.[buildDepStep] (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\arborist\build-ideal-tree.js:631:8)
1904 verbose stack at async Arborist.buildIdealTree (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\arborist\build-ideal-tree.js:166:7)
1904 verbose stack at async Promise.all (index 1)
1904 verbose stack at async Arborist.reify (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\arborist\reify.js:125:5)
1904 verbose stack at async install (C:\Program Files\nodejs\node_modules\npm\lib\install.js:40:5)
1905 verbose cwd C:\Users\...\VisualStudioCodeWorkspace\light-webapp
1906 verbose Windows_NT 10.0.18363
1907 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--quiet"
1908 verbose node v12.18.1
1909 verbose npm v7.0.0-beta.8
1910 error code ERESOLVE
1911 error unable to resolve dependency tree
Any ideas why node is failing on such a simple command?
Installing the latest versions of node and npm separately solved my issue.
Related
My expo project doesn't start when I try to use expo start.
Node Version - v12.18.1
Expo Version - 3.21.10
When i run expo start:
Error: react-native is not installed. Please run `npm install` or `yarn` in your project directory.
Couldn't start project. Please fix the errors and restart the project.
Error: Couldn't start project. Please fix the errors and restart the project.
at startExpoServerAsync (C:\#expo\xdl#57.9.18\src\Project.ts:2070:11)
at Object.startAsync (C:\#expo\xdl#57.9.18\src\Project.ts:2384:5)
at action (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\src\commands\start.ts:181:3)
at C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\src\commands\start.ts:354:16
at Command.<anonymous> (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\src\exp.ts:80:7)
Then I ran npm install mentioned in the above error but then got this error
npm ERR! code ERR_OSSL_PEM_NO_START_LINE
npm ERR! error:0909006C:PEM routines:get_name:no start line
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Admin\AppData\Roaming\npm-cache\_logs\2020-06-26T05_41_06_628Z-debug.log
This is my error log file
1212 silly saveTree +-- react-navigation#4.3.9
1212 silly saveTree +-- react#16.9.0
1212 silly saveTree +-- redux#4.0.5
1212 silly saveTree `-- yarn#1.22.4
1213 verbose stack Error: error:0909006C:PEM routines:get_name:no start line
1213 verbose stack at Object.createSecureContext (_tls_common.js:149:17)
1213 verbose stack at Object.connect (_tls_wrap.js:1588:48)
1213 verbose stack at HttpsAgent.createConnection (https.js:130:22)
1213 verbose stack at HttpsAgent.createSocket (C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\agentkeepalive\lib\_http_agent.js:265:26)
1213 verbose stack at HttpsAgent.createSocket (C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\agentkeepalive\lib\agent.js:77:11)
1213 verbose stack at HttpsAgent.addRequest (C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\agentkeepalive\lib\_http_agent.js:239:10)
1213 verbose stack at new ClientRequest (_http_client.js:296:16)
1213 verbose stack at request (https.js:314:10)
1213 verbose stack at C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\node-fetch-npm\src\index.js:54:17
1213 verbose stack at new Promise (<anonymous>)
1213 verbose stack at fetch (C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\node-fetch-npm\src\index.js:41:10)
1213 verbose stack at C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\make-fetch-happen\index.js:332:14
1213 verbose stack at C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\promise-retry\index.js:29:24
1214 verbose cwd D:\React\customer-app
1215 verbose Windows_NT 10.0.18362
1216 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Admin\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
1217 verbose node v12.18.0
1218 verbose npm v6.14.5
1219 error code ERR_OSSL_PEM_NO_START_LINE
1220 error error:0909006C:PEM routines:get_name:no start line
1221 verbose exit [ 1, true ]
Please help me how to resolve this error!
Try doing this before
npm set registry http://registry.npmjs.org/
https://stackoverflow.com/a/57195189
My npm version: 6.4.1
node: 10.14.1
Ionic: 4.7.0
Cordova: 8.1.2 (Basically all of them are of the latest version)
When I try to install an ionic sidemenu at a specific location, an error occurs as such:
npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on
reading Browserslist >3.0 config used in other tools.
npm ERR! code Z_BUF_ERROR
npm ERR! errno -5
npm ERR! zlib: unexpected end of file
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\15432\AppData\Roaming\npm-cache\_logs\2019-01-
12T00_54_51_838Z-debug.log
So I navigate to the log document and have a look on the end of the file:
1474 silly saveTree | +-- path-to-regexp#1.7.0
1474 silly saveTree | | `-- isarray#0.0.1
1474 silly saveTree | `-- serviceworker-cache-polyfill#4.0.0
1474 silly saveTree `-- zone.js#0.8.26
1475 verbose stack ZlibError: zlib: unexpected end of file
1475 verbose stack at Zlib.(anonymous function).onerror (C:\Program
Files\nodejs\node_modules\npm\node_modules\minizlib\index.js:131:21)
1475 verbose stack at Unzip.write (C:\Program
Files\nodejs\node_modules\npm\node_modules\minizlib\index.js:255:31)
1475 verbose stack at Unzip.flush (C:\Program
Files\nodejs\node_modules\npm\node_modules\minizlib\index.js:222:10)
1475 verbose stack at Unzip.end (C:\Program
Files\nodejs\node_modules\npm\node_modules\minizlib\index.js:229:10)
1475 verbose stack at Object.end (C:\Program
Files\nodejs\node_modules\npm\node_modules\tar\lib\parse.js:415:21)
1475 verbose stack at PassThrough.onend (_stream_readable.js:628:10)
1475 verbose stack at Object.onceWrapper (events.js:273:13)
1475 verbose stack at PassThrough.emit (events.js:187:15)
1475 verbose stack at endReadableNT (_stream_readable.js:1094:12)
1475 verbose stack at process._tickCallback
(internal/process/next_tick.js:63:19)
1476 verbose cwd D:\Coursera Doc\Ionic\conFusion
1477 verbose Windows_NT 10.0.17134
1478 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program
Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
1479 verbose node v10.14.1
1480 verbose npm v6.4.1
1481 error code Z_BUF_ERROR
1482 error errno -5
1483 error zlib: unexpected end of file
1484 verbose exit [ -5, true ]
I really have no idea what this means. So I try to type "npm install" and fix all the problems on the subfolder in which I create my sidemenu, and the same issue, as above, occurs.
I hope that anyone can help me address this issue.
This problem seems to be a DNS issue when connecting to npm registry.
Please check (https://status.npmjs.org/) first to see if all services are operational then clear your npm cache.
Force clean your npm cache by doing:
npm cache clean --force
I faced this issue with the node version 10.15.0 installed on my machine. I got a very similar error while installing the ts-node-dev.
npm ERR! code Z_BUF_ERROR
npm ERR! errno -5
npm ERR! zlib: unexpected end of file
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xyz\AppData\Roaming\npm-cache\_logs\2021-11-30T07_38_27_700Z-debug.log
I tried the npm cache clean --force command but that didn't solve the problem.
Finally, I upgraded my node to version 16.13.0 and that solved the issue.
I am trying to develop my first android app using react-native and expo for testing, on windows 8.1.
Working from a tutorial I had a working project using react-native components but everything broke when I installed a dependency with
`npm install --save react-navigation`:
npm-start returned
Error: React native is not installed. Please run 'npm install' in your project directory.
So I ran npm-install again as suggested.
This led to npm-start asking me if I want to install expo-cli globally, and whether I answer yes or no I get the following error:
Installing the package [expo-cli][1]...
events.js:167
throw er; // Unhandled 'error' event
^
Error: spawn npm ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! empty-project-template# start: `expo start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the empty-project-template# 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\me\AppData\Roaming\npm-cache\_logs\2018-09-25T21_27_21_053Z-debug.log
The log mentioned in this message is as follows:
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 'start' ]
2 info using npm#6.4.1
3 info using node#v10.11.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle empty-project-template#~prestart: empty-project-template#
6 info lifecycle empty-project-template#~start: empty-project-template#
7 verbose lifecycle empty-project-template#~start: unsafe-perm in lifecycle true
8 verbose lifecycle empty-project-template#~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\androidProjects\MoviesAndMe\node_modules\.bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\libnvvp;C:\ProgramData\Anaconda3;C:\ProgramData\Anaconda3\Library\mingw-w64\bin;C:\ProgramData\Anaconda3\Library\usr\bin;C:\ProgramData\Anaconda3\Library\bin;C:\ProgramData\Anaconda3\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Skype\Phone\;C:\Android;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Users\me\Documents\Latex\miktex\bin\;C:\Users\me\AppData\Local\atom\bin;C:\Users\me\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Program Files\Java\jdk1.8.0_181\bin;C:\Users\me\AppData\Roaming\npm
9 verbose lifecycle empty-project-template#~start: CWD: D:\androidProjects\MoviesAndMe
10 silly lifecycle empty-project-template#~start: Args: [ '/d /s /c', 'expo start' ]
11 silly lifecycle empty-project-template#~start: Returned: code: 1 signal: null
12 info lifecycle empty-project-template#~start: Failed to exec start script
13 verbose stack Error: empty-project-template# start: `expo start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (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.<anonymous> (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 empty-project-template#
15 verbose cwd D:\androidProjects\MoviesAndMe
16 verbose Windows_NT 6.3.9600
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v10.11.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error empty-project-template# start: `expo start`
22 error Exit status 1
23 error Failed at the empty-project-template# start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I searched on StackOverflow and followed the advice to deal with ELIFECYCLE errors found in this answer. runnning npm cache clean then deleting the node_modules directory and package-lock.json buit the error is the same.
I even tried doing these steps as well as removing the react-navigation from my dependencies in my package.json file and in my code before running npm-install again, but it didn't change anything.
It is interesting to note that when running expo start on it's own it manages to launch the bundler and the devtools in the browser just not with the right ip address.
I also don't know if this is important but when running npm-install I get 2 vulnerabilities, when I run npm-audit it indicates that the is a low 'Prototype Pollution' vulnerability in the lodash package and a High 'Denial of Service' vulnerability in the ws package. But nothing changes even after running npm audit fix
Anyway I hope you can help me, thanks!
I was having the same problem.
If you run:
npm i expo-cli
and then
npm start
It will work
In my case, angular-cli was not installed so I ran the command as -
npm install -g angular-cli
I am getting this error when trying to install nodemon in a brand new node project.
I've created a blank folder named my-project
then, inside it, I've executed to creeate a package.json file:
npm init -f
then when tryed to run
npm install --save-dev nodemon
And that was the result:
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for timed-out
I've just update my node version to the latest one and so npm tools.
node --version -> v8.9.4
npm --version -> 5.6.0
The funny part is that I've done this same steps in another computer 2 days ago with no problem.
325 verbose stack timed-out: No valid versions available for timed-out
325 verbose stack at pickManifest (C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\npm-pick-manifest\index.js:20:11)
325 verbose stack at fetchPackument.then.packument (C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\lib\fetchers\registry\manifest.js:39:14)
325 verbose stack at tryCatcher (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
325 verbose stack at Promise._settlePromiseFromHandler (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\promise.js:512:31)
325 verbose stack at Promise._settlePromise (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\promise.js:569:18)
325 verbose stack at Promise._settlePromise0 (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\promise.js:614:10)
325 verbose stack at Promise._settlePromises (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\promise.js:693:18)
325 verbose stack at Async._drainQueue (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\async.js:133:16)
325 verbose stack at Async._drainQueues (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\async.js:143:10)
325 verbose stack at Immediate.Async.drainQueues (C:\Program Files\nodejs\node_modules\npm\node_modules\bluebird\js\release\async.js:17:14)
325 verbose stack at runCallback (timers.js:789:20)
325 verbose stack at tryOnImmediate (timers.js:751:5)
325 verbose stack at processImmediate [as _immediateCallback] (timers.js:722:5)
326 verbose cwd E:\githubprojects\my-project\server
327 verbose Windows_NT 10.0.16299
328 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save-dev" "nodemon#v1.14.7"
329 verbose node v8.9.4
330 verbose npm v5.6.0
331 error code ENOVERSIONS
332 error No valid versions available for timed-out
333 verbose exit [ 1, true ]
Official issue: https://github.com/npm/registry/issues/255
Official status: https://status.npmjs.org/incidents/41zfb8qpvrdj
Several packages including "require-from-string" are currently unavailable. We are aware of the issue and are working to restore the affected user and packages. Please do not attempt to republish packages, as this will hinder our progress in restoring them.
Update from NPM:
Resolved
We apologize for the temporary unavailability of some packages. We will be publishing a comprehensive post-mortem update in the next few days.
Posted Jan 06, 2018 - 23:14 UTC
timed-out is a npm package that is apparently missing, as of the last day, or hour, or minutes (I don't know the time span).
/Users/Stan ==> npm install timed-out -g
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for timed-out
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/Stan/.npm/_logs/2018-01-06T20_26_40_854Z-debug.log
Now it is working.
/Users/Stan ==> npm install timed-out -g
+ timed-out#4.0.1
added 1 package in 1.306s
It's not you, it's an already known issue, due to dependency problems.
More details here https://github.com/remy/nodemon/issues/1210
Users are reporting that packages are being made available again. Try again and see if your issue is resolved.
https://github.com/npm/registry/issues/255
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.