kickstart throws error 130

[glantucan]

It's odd because it seems to work afterwards, but don't know if I'll find more issues later because of this. Here is the output of the 'npm kickstart' command

 npm run kickstart

> webpack-starter-basic@2.0.0 kickstart /home/glantruan/_programming/personal/all-fred
> node kickstarter

? What's the name of your project? (kebab-cased) (awesome-project) AllFred
? What's the name of your project? (kebab-cased) AllFred
? Who's the author? (John Doe) Glantucan
? Who's the author? Glantucan
? What color would you like the mobile header to be? (https://bit.ly/1LX2mtq) (#ff4970) #ff4970
? What color would you like the mobile header to be? (https://bit.ly/1LX2mtq) #ff4970
Removing /docs directory
Updating package.json name
Updating package.json author
Removing package.json git repository
Removing package.json kickstart dependencies
Removing package.json kickstart script
Writing new package.json
Removing package-lock.json
Setting mobile header color to #ff4970
Setting page title to project name
Writing new index.html
Writing new webpack.prod.js
Removing kickstarter script
Removing .git directory
All done!
npm ERR! code ELIFECYCLE
npm ERR! errno 130
npm ERR! webpack-starter-basic@2.0.0 kickstart: `node kickstarter`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the webpack-starter-basic@2.0.0 kickstart 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/glantruan/.npm/_logs/2018-12-06T14_55_21_878Z-debug.log

And here is the log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'kickstart' ]
2 info using npm@6.4.1
3 info using node@v10.14.1
4 verbose run-script [ 'prekickstart', 'kickstart', 'postkickstart' ]
5 info lifecycle webpack-starter-basic@2.0.0~prekickstart: webpack-starter-basic@2.0.0
6 info lifecycle webpack-starter-basic@2.0.0~kickstart: webpack-starter-basic@2.0.0
7 verbose lifecycle webpack-starter-basic@2.0.0~kickstart: unsafe-perm in lifecycle true
8 verbose lifecycle webpack-starter-basic@2.0.0~kickstart: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/glantruan/_programming/personal/all-fred/node_modules/.bin:/home/glantruan/bin:/home/glantruan/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle webpack-starter-basic@2.0.0~kickstart: CWD: /home/glantruan/_programming/personal/all-fred
10 silly lifecycle webpack-starter-basic@2.0.0~kickstart: Args: [ '-c', 'node kickstarter' ]
11 silly lifecycle webpack-starter-basic@2.0.0~kickstart: Returned: code: 130  signal: null
12 info lifecycle webpack-starter-basic@2.0.0~kickstart: Failed to exec kickstart script
13 verbose stack Error: webpack-starter-basic@2.0.0 kickstart: `node kickstarter`
13 verbose stack Exit status 130
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/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> (/usr/lib/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 webpack-starter-basic@2.0.0
15 verbose cwd /home/glantruan/_programming/personal/all-fred
16 verbose Linux 4.15.0-38-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "kickstart"
18 verbose node v10.14.1
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 130
22 error webpack-starter-basic@2.0.0 kickstart: `node kickstarter`
22 error Exit status 130
23 error Failed at the webpack-starter-basic@2.0.0 kickstart script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 130, true ]

[lifenautjoe]

Hi @glantucan ,

Thanks for the report. I will take a look today.

[lifenautjoe]

Hello again.

I couldn't reproduce the error. I see in the log however and reading similar issues that this might have to do with the compiled platform dependent C libraries that node uses. (https://github.com/nodejs/node-gyp)

It's suggested to do one of the following

• Remove the node_modules and npm install again
• Reinstall node

I'll keep looking on my side if there's something I can do to handle this.

[lifenautjoe]

Tried on some other environments. Could not reproduce. Closing for now.