Keep having problems with npm run watch

[snake2401]

I seem to keep on having problems with running the npm commands... After nmp install i try to run the watch script but seems to get the error:

npm ERR! code ELIFECYCLE
npm ERR! errno 1

I dont know if it 's got something to do with the luxe config, but my other luxe projects seem to have no problems...
Cleared my caches, dit a reintall, updates node, run audit fixes...

[brettsmason]

Hi @snake2401 I've not experienced that myself.
Have you tried deleting the node_modules folder? Eg rm -r node_modules?
Is this a fresh copy of Luxe, or has it been modified at all?

[snake2401]

It was a local copy of a existing install. I copied the folder to another project. Already tried to remove the node_modules and installed it again using npm install. Didn’t work. Maybe I will create a second theme using a clean install and copy my modified files to it.

…

Op 16 sep. 2020 om 20:26 heeft Brett Mason ***@***.***> het volgende geschreven:  Hi @snake2401 I've not experienced that myself. Have you tried deleting the node_modules folder? Eg rm -r node_modules? Is this a fresh copy of Luxe, or has it been modified at all? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[snake2401]

Nope…. When a do a clean install I get warnings about my node version (see below). I am on node 9.11.1. What is the right version I must use? npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10.14","npm":">=6","yarn":">=1"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">= 10.13.0"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^8.10.0 || ^10.13.0 || >=11.10.1"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10.0.0"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">= 10.13.0"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^8.16.0 || ^10.6.0 || >=11.0.0"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"6.* || 8.* || >= 10.*"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">= 10"} (current: {"node":"9.11.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=10"} (current: {"node":"9.11.1","npm":"6.14.4"})

…

Op 16 sep. 2020, om 21:27 heeft Herco Terweij ***@***.***> het volgende geschreven: It was a local copy of a existing install. I copied the folder to another project. Already tried to remove the node_modules and installed it again using npm install. Didn’t work. Maybe I will create a second theme using a clean install and copy my modified files to it. > Op 16 sep. 2020 om 20:26 heeft Brett Mason ***@***.***> het volgende geschreven: > >  > > Hi @snake2401 <https://github.com/snake2401> I've not experienced that myself. > Have you tried deleting the node_modules folder? Eg rm -r node_modules? > Is this a fresh copy of Luxe, or has it been modified at all? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <#244 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJRSWYIMDGJ4BZJ2H67VGTTSGD7MTANCNFSM4RO3RVPA>. >

[tiborp]

See error message:
wanted: {"node":">=10.14","npm":">=6","yarn":">=1"} (current: {"node":"9.11.1","npm":"6.14.4"})

[snake2401]

Yep I saw that, that was not the whole problem thought… Got it working now. The reason why I moved it to e new environment was because is downloaded e new version of Local. From there on my cpu went overboard (over 400%) when I ran the watch script and kept on compiling over and over… Turns out that the new local has a similar browsersync that conflicted rich de nmp script… Oke, after ours of searching, I can continu on my project… THX for the suggestions you guys

…

Op 17 sep. 2020, om 07:24 heeft Tibor Paulsch ***@***.***> het volgende geschreven: See error message: wanted: {"node":">=10.14","npm":">=6","yarn":">=1"} (current: {"node":"9.11.1","npm":"6.14.4"}) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#244 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJRSWYOJDRTTJ7TGQPA7J5LSGGMPHANCNFSM4RO3RVPA>.

[brettsmason]

Glad you got it working, and thanks @tiborp for helping out 😃
I'd suggest running at least the most up to date LTS version of node (12.18.4 at the moment).