I'm having the following error when running 'npm run build' for my app.
⠋ building for production.../home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/last-call-webpack-plugin/src/index.js:170
compiler.hooks.compilation.tap(
^
TypeError: Cannot read property 'compilation' of undefined
at OptimizeCssAssetsWebpackPlugin.apply (/home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/last-call-webpack-plugin/src/index.js:170:20)
at Compiler.apply (/home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/tapable/lib/Tapable.js:375:16)
at webpack (/home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/webpack/lib/webpack.js:33:19)
at err (/home/edu/Dropbox/projects/personal/for good/musixshare/build/build.js:19:3)
at next (/home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/rimraf/rimraf.js:75:7)
at CB (/home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/rimraf/rimraf.js:111:9)
at /home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/rimraf/rimraf.js:137:14
at FSReqWrap.oncomplete (fs.js:152:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! musixshare#1.0.0 build: `node build/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the musixshare#1.0.0 build 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! /home/edu/.npm/_logs/2018-05-25T17_24_14_199Z-debug.log
And this is the error log I got:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.1.0
3 info using node#v8.11.2
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle musixshare#1.0.0~prebuild: musixshare#1.0.0
6 info lifecycle musixshare#1.0.0~build: musixshare#1.0.0
7 verbose lifecycle musixshare#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle musixshare#1.0.0~build: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/edu/Dropbox/projects/personal/for good/musixshare/node_modules/.bin:/home/edu/bin:/home/edu/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle musixshare#1.0.0~build: CWD: /home/edu/Dropbox/projects/personal/for good/musixshare
10 silly lifecycle musixshare#1.0.0~build: Args: [ '-c', 'node build/build.js' ]
11 silly lifecycle musixshare#1.0.0~build: Returned: code: 1 signal: null
12 info lifecycle musixshare#1.0.0~build: Failed to exec build script
13 verbose stack Error: musixshare#1.0.0 build: `node build/build.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid musixshare#1.0.0
15 verbose cwd /home/edu/Dropbox/projects/personal/for good/musixshare
16 verbose Linux 4.13.0-43-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v8.11.2
19 verbose npm v6.1.0
20 error code ELIFECYCLE
21 error errno 1
22 error musixshare#1.0.0 build: `node build/build.js`
22 error Exit status 1
23 error Failed at the musixshare#1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
How can I solve this? I can run 'npm run dev' normally, just the build return this error. I've already tried updating all the dependencies.
I've got the solution, the problem was a incompatibility between webpack and optimize-css-assets-webpack-plugin. Downgrading the package to v3.2.0 got it fixed.
Related
In my project, I'm using VueCli for the frontend. Now what I'm trying to do is deploy my project which is in remote server into the actual server. I'm using npm run build command to build the frontend first. But I can't build my project since the following error occurs again and again
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mobile-h5#0.1.0 build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mobile-h5#0.1.0 build 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/daisywu/.npm/_logs/2021-09-24T06_13_06_000Z-debug.log
I delete package-lock.json and node_modules,then do npm cache clean --force,then do npm install,Still unable to construct
debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.9
3 info using node#v14.15.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mobile-h5#0.1.0~prebuild: mobile-h5#0.1.0
6 info lifecycle mobile-h5#0.1.0~build: mobile-h5#0.1.0
7 verbose lifecycle mobile-h5#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle mobile-h5#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/daisywu/Documents/mobile-h5/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle mobile-h5#0.1.0~build: CWD: /Users/daisywu/Documents/mobile-h5
10 silly lifecycle mobile-h5#0.1.0~build: Args: [ '-c', 'vue-cli-service build' ]
11 silly lifecycle mobile-h5#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle mobile-h5#0.1.0~build: Failed to exec build script
13 verbose stack Error: mobile-h5#0.1.0 build: `vue-cli-service build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid mobile-h5#0.1.0
15 verbose cwd /Users/daisywu/Documents/mobile-h5
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.15.3
19 verbose npm v6.14.9
20 error code ELIFECYCLE
21 error errno 1
22 error mobile-h5#0.1.0 build: `vue-cli-service build`
22 error Exit status 1
23 error Failed at the mobile-h5#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Please help thank you
The reason is insufficient memory. Update the answer for your reference
Written in package.json
"build": "node --max_old_space_size=4096 node_modules/#vue/cli-service/bin/vue-cli-service.js build --mode development"
do npm run build
Trying to compile theme (named foo) in Prestashop:
cd themes/foo/_dev
npm run build
Get the following error.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! prestashop-classic-dev-tools#1.0.0 build: `webpack`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the prestashop-classic-dev-tools#1.0.0 build 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! /root/.npm/_logs/2021-07-02T05_58_35_445Z-debug.log
Here is the log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.14.13
3 info using node#v14.17.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle prestashop-classic-dev-tools#1.0.0~prebuild: prestashop-classic-dev-tools#1.0.0
6 info lifecycle prestashop-classic-dev-tools#1.0.0~build: prestashop-classic-dev-tools#1.0.0
7 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: PATH: /usr/lib/node_modules/npm/node_mod$
9 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: CWD: /var/www/html/themes/foo$
10 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Args: [ '-c', 'webpack' ]
11 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Returned: code: 2 signal: null
12 info lifecycle prestashop-classic-dev-tools#1.0.0~build: Failed to exec build script
13 verbose stack Error: prestashop-classic-dev-tools#1.0.0 build: `webpack`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at EventEmitter.emit (events.js:376:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at ChildProcess.emit (events.js:376:20)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid prestashop-classic-dev-tools#1.0.0
15 verbose cwd /var/www/html/themes/foo/_dev
16 verbose Linux 5.8.0-59-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v14.17.0
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 2
22 error prestashop-classic-dev-tools#1.0.0 build: `webpack`
22 error Exit status 2
23 error Failed at the prestashop-classic-dev-tools#1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
npm version is:
> npm -v
6.14.13
What could be the cause?
Cause of the issue not found. Resolved with the following commands:
Clean npm cache
> npm cache clean --force
Remove node modules
> rm -rf node_modules package-lock.json
Install npm
> npm install
Run build
> npm run build
I'm totally new to prestashop development and all of that stuff and if u reply pls use simplest explanation possible. I'm actually new to web tech too. There is a problem with webpack when im trying to use 'npm run watch' and it says
[webpack-cli] TypeError: compiler.plugin is not a function
at ExtractTextPlugin.apply (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\extract-text-webpack-plugin\index.js:233:11)
at createCompiler (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\webpack.js:69:12)
at create (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\webpack.js:113:15)
at webpack (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\webpack.js:121:46)
at f (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\index.js:37:15)
at WebpackCLI.createCompiler (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:1337:24)
at async WebpackCLI.bundleCommand (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:1433:20)
at async Command. (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:384:25)
at async Promise.all (index 1)
at async Command. (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:824:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! prestashop-classic-dev-tools#1.0.0 watch: webpack --progress --watch
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the prestashop-classic-dev-tools#1.0.0 watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
the complete log is
> 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:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'watch'
1 verbose cli ]
2 info using npm#6.14.10
3 info using node#v14.15.4
4 verbose run-script [ 'prewatch', 'watch', 'postwatch' ]
5 info lifecycle prestashop-classic-dev-tools#1.0.0~prewatch: prestashop-classic-dev-tools#1.0.0
6 info lifecycle prestashop-classic-dev-tools#1.0.0~watch: prestashop-classic-dev-tools#1.0.0
7 verbose lifecycle prestashop-classic-dev-tools#1.0.0~watch: unsafe-perm in lifecycle true
8 verbose lifecycle prestashop-classic-dev-tools#1.0.0~watch: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\xampp\htdocs\prestashop\themes\classic\_dev\node_modules\.bin;C:\Users\ja\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\ja\bin;C:\Python39\Scripts;C:\Python39;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\ProgramData\chocolatey\bin;C:\Program Files\Git\cmd;C:\Program Files\nodejs;C:\Program Files\MySQL\MySQL Server 8.0\bin;C:\Program Files\MySQL\MySQL Shell 8.0\bin;C:\Users\ja\AppData\Local\Programs\Python\Python38\Scripts;C:\Users\ja\AppData\Local\Programs\Python\Python38;C:\Users\ja\geckodriver.exe;C:\Users\ja\AppData\Local\Microsoft\WindowsApps;C:\Users\ja\AppData\Local\Programs\Microsoft VS Code\bin;C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin;C:\Users\ja\.pyenv\pyenv-win\bin;C:\Users\ja\.pyenv\pyenv-win\shims;C:\xampp\php;C:\Users\ja\AppData\Roaming\npm;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle prestashop-classic-dev-tools#1.0.0~watch: CWD: C:\xampp\htdocs\prestashop\themes\classic\_dev
10 silly lifecycle prestashop-classic-dev-tools#1.0.0~watch: Args: [ '/d /s /c', 'webpack --progress --watch' ]
11 silly lifecycle prestashop-classic-dev-tools#1.0.0~watch: Returned: code: 2 signal: null
12 info lifecycle prestashop-classic-dev-tools#1.0.0~watch: Failed to exec watch script
13 verbose stack Error: prestashop-classic-dev-tools#1.0.0 watch: `webpack --progress --watch`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
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:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid prestashop-classic-dev-tools#1.0.0
15 verbose cwd C:\xampp\htdocs\prestashop\themes\classic\_dev
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "watch"
18 verbose node v14.15.4
19 verbose npm v6.14.10
20 error code ELIFECYCLE
21 error errno 2
22 error prestashop-classic-dev-tools#1.0.0 watch: `webpack --progress --watch`
22 error Exit status 2
23 error Failed at the prestashop-classic-dev-tools#1.0.0 watch script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
I already tried to reinstall Node and webpack and also tried to run this with my antivirus off but nothing seems to work
I got error message 'not finished load plugins', when I trying to load local server with [npm run develop]
What should I do?
This is the error message I got:
not finished load plugins - 0.975s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Henisis#0.2.0 develop: `GATSBY_ENV=staging gatsby develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the Henisis#0.2.0 develop 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/mingyeongso/.npm/_logs/2020-04-08T06_51_49_655Z-debug.log
mingyeongui-MacBookPro:henesis-website mingyeongso$
From the debug file:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'develop' ]
2 info using npm#6.14.2
3 info using node#v10.16.3
4 verbose run-script [ 'predevelop', 'develop', 'postdevelop' ]
5 info lifecycle Henisis#0.2.0~predevelop: Henisis#0.2.0
6 info lifecycle Henisis#0.2.0~develop: Henisis#0.2.0
7 verbose lifecycle Henisis#0.2.0~develop: unsafe-perm in lifecycle true
8 verbose lifecycle Henisis#0.2.0~develop: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/mingyeongso/Documents/GitHub/henesis-website/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle Henisis#0.2.0~develop: CWD: /Users/mingyeongso/Documents/GitHub/henesis-website
10 silly lifecycle Henisis#0.2.0~develop: Args: [ '-c', 'GATSBY_ENV=staging gatsby develop' ]
11 silly lifecycle Henisis#0.2.0~develop: Returned: code: 1 signal: null
12 info lifecycle Henisis#0.2.0~develop: Failed to exec develop script
13 verbose stack Error: Henisis#0.2.0 develop: GATSBY_ENV=staging gatsby develop
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/local/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 Henisis#0.2.0
15 verbose cwd /Users/mingyeongso/Documents/GitHub/henesis-website
16 verbose Darwin 18.7.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "develop"
18 verbose node v10.16.3
19 verbose npm v6.14.2
20 error code ELIFECYCLE
21 error errno 1
22 error Henisis#0.2.0 develop: GATSBY_ENV=staging gatsby develop
22 error Exit status 1
23 error Failed at the Henisis#0.2.0 develop script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I resolved this error by this:
npm cache clean --force
delete package-lock.json file
npm install
I receive an error when using "npm start" it throws me this error.
I've already tried npm-cache-clean , and also trying delete the node_modules as well as deleting the package-lock.json , followed by "npm install" this didn't yield a different result.
npm ERR! code ELIFECYCLE
npm ERR! errno 77
npm ERR! crimstock#1.0.0 start: `electron .`
npm ERR! Exit status 77
npm ERR!
npm ERR! Failed at the crimstock#1.0.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\Negus\AppData\Roaming\npm-cache\_logs\2019-04-23T04_45_49_315Z-debug.log
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#v8.12.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle crimstock#1.0.0~prestart: crimstock#1.0.0
6 info lifecycle crimstock#1.0.0~start: crimstock#1.0.0
7 verbose lifecycle crimstock#1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle crimstock#1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\Desktop\Crimstock2\node_modules\.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\Negus\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\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:\Users\Negus\Desktop\Code\phantomjs-2.1.1-windows\phantomjs-2.1.1-windows\bin;C:\Program Files\Git\cmd;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\nodejs;C:\Users\Negus\AppData\Local\Programs\Python\Python36-32\Scripts;C:\Users\Negus\AppData\Local\Programs\Python\Python36-32;C:\Phantom\phantomjs-2.1.1-windows\bin;C:\Users\Negus\AppData\Roaming\npm;C:\Users\Negus\AppData\Local\Microsoft\WindowsApps;C:\Mongodb\bin;C:\Program Files\heroku\bin
9 verbose lifecycle crimstock#1.0.0~start: CWD: D:\Desktop\Crimstock2
10 silly lifecycle crimstock#1.0.0~start: Args: [ '/d /s /c', 'electron .' ]
11 silly lifecycle crimstock#1.0.0~start: Returned: code: 77 signal: null
12 info lifecycle crimstock#1.0.0~start: Failed to exec start script
13 verbose stack Error: crimstock#1.0.0 start: `electron .`
13 verbose stack Exit status 77
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 emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
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 emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid crimstock#1.0.0
15 verbose cwd D:\Desktop\Crimstock2
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v8.12.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 77
22 error crimstock#1.0.0 start: `electron .`
22 error Exit status 77
23 error Failed at the crimstock#1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 77, true ]
I want the electron app to start and not throw and error because I can't test any javascript in the index.js file I have