Azure functions node error when doing npm start - node.js

I am trying to run my azure functions locally by doing npm start or even the simple func start.
It was working perfectly until today when the following error started coming:
The func.deps.json file is here: C:\Program Files\Microsoft\Azure Functions Core Tools and it has the dependency below.
I don't even use this and don't know what it is "Error: An assembly specified in the application dependencies manifest (func.deps.json) was not found: package: 'Marklio.Metadata', version: '1.2.20-beta' path: 'lib/netstandard2.0/Marklio.Metadata.dll' npm "
xxx-api#0.0.1 build:docs C:\Code\xxxx-api
> tsc --sourcemap --lib es2017 src/_doc/index.ts --outDir doc && node doc/index.js
Error:
An assembly specified in the application dependencies manifest (func.deps.json) was not found:
package: 'Marklio.Metadata', version: '1.2.20-beta'
path: 'lib/netstandard2.0/Marklio.Metadata.dll'
npm ERR! code ELIFECYCLE
npm ERR! errno 2147516556
npm ERR! xxxx-api#0.0.1 install:extensions: `npm run build && cross-var func extensions install --prefix
$npm_package_config_azureFunctions_outDir`
npm ERR! Exit status 2147516556
npm ERR!
npm ERR! Failed at the xxx-api#0.0.1 install:extensions 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-08-13T04_37_33_194Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2147516556
npm ERR! panthera-api#0.0.1 install:extensions: `npm run build && cross-var func extensions install --prefix
$npm_package_config_azureFunctions_outDir`
npm ERR! Exit status 2147516556
npm ERR!
npm ERR! Failed at the xx-api#0.0.1 install:extensions 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\xx\AppData\Roaming\npm-cache\_logs\2020-08-13T04_37_33_194Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2147516556
npm ERR! xx-api#0.0.1 prestart: `npm run install:extensions`
npm ERR! Exit status 2147516556
npm ERR!
npm ERR! Failed at the xxx-api#0.0.1 prestart 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\xx\AppData\Roaming\npm-cache\_logs\2020-08-13T04_37_33_241Z-debug.log
My package.json file scripts are as follows:
"scripts": {
"build": "npm run clean && tsc && npm run build:configFiles && npm run build:docs",
"build:production": "npm run prestart && cross-var rimraf $npm_package_config_azureFunctions_outDir/local.*.json && cross-var copyfiles package.json $npm_package_config_azureFunctions_outDir && cd dist && npm install --production",
"build:configFiles": "cross-var copyfiles -u 1 \"$npm_package_config_azureFunctions_rootDir/**/*.json\" $npm_package_config_azureFunctions_outDir",
"build:docs": "tsc --sourcemap --lib es2017 src/_doc/index.ts --outDir doc && node doc/index.js",
"prestart": "npm run install:extensions",
"start": "npm-run-all -p start:host watch watch:config",
"start:doc": "npm run install:extensions && npm run start:host",
"start:host": "cross-var func host start --prefix $npm_package_config_azureFunctions_outDir",
"watch": "tsc --w",
"watch:config": "cross-var onchange \"$npm_package_config_azureFunctions_rootDir/**/*.json\" -- npm run build:configFiles",
"clean": "cross-var rimraf $npm_package_config_azureFunctions_outDir",
"install:extensions": "npm run build && cross-var func extensions install --prefix $npm_package_config_azureFunctions_outDir",
"install:extensions:force": "npm run build && cross-var func extensions install --prefix $npm_package_config_azureFunctions_outDir --force",
"test": "jest",
"precommit-msg": "echo 'Pre-commit checks...' && exit 0",
"fix": "eslint --ext .ts --fix ",
"fix-dry-run": "eslint --ext .ts --fix-dry-run",
"lint": "eslint . --ext .ts"
},
Finally, the contents of the log file mentioned above:
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 'install:extensions'
1 verbose cli ]
2 info using npm#6.14.5
3 info using node#v12.18.1
4 verbose run-script [
4 verbose run-script 'preinstall:extensions',
4 verbose run-script 'install:extensions',
4 verbose run-script 'postinstall:extensions'
4 verbose run-script ]
5 info lifecycle xxx-api#0.0.1~preinstall:extensions: xxx-api#0.0.1
6 info lifecycle xxx-api#0.0.1~install:extensions: xxx-api#0.0.1
7 verbose lifecycle xxx-api#0.0.1~install:extensions: unsafe-perm in lifecycle true
8 verbose lifecycle xxx-api#0.0.1~install:extensions: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Code\xxxAPI\xxx-api\node_modules\.bin;C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Code\xxxAPI\xxx-api\node_modules\.bin;C:\Users\xxx Sharma.STATEMERCANTILE\AppData\Roaming\npm;C:\Program Files\Common Files\Microsoft Shared\Microsoft Online Services;C:\Program Files (x86)\Common Files\Microsoft Shared\Microsoft Online Services;C:\Program Files\Microsoft MPI\Bin\;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Seq\;C:\Program Files\Seq\Client\;C:\Program Files\dotnet\;C:\Program Files\nodejs\;C:\Program Files\Microsoft\Azure Functions Core Tools\;C:\Program Files (x86)\GitExtensions\;C:\Program Files (x86)\dotnet\;C:\Users\xxx Sharma.STATEMERCANTILE\AppData\Roaming\npm;C:\Users\xxx Sharma.STATEMERCANTILE\AppData\Local\Microsoft\WindowsApps;C:\Users\xxx Sharma.STATEMERCANTILE\.dotnet\tools;C:\Users\xxx Sharma.STATEMERCANTILE\AppData\Local\Programs\Microsoft VS Code\bin;
9 verbose lifecycle xxx-api#0.0.1~install:extensions: CWD: C:\Code\xxxAPI\xxx-api
10 silly lifecycle xxx-api#0.0.1~install:extensions: Args: [
10 silly lifecycle '/d /s /c',
10 silly lifecycle 'npm run build && cross-var func extensions install --prefix $npm_package_config_azureFunctions_outDir'
10 silly lifecycle ]
11 silly lifecycle xxx-api#0.0.1~install:extensions: Returned: code: 2147516556 signal: null
12 info lifecycle xxx-api#0.0.1~install:extensions: Failed to exec install:extensions script
13 verbose stack Error: xxx-api#0.0.1 install:extensions: `npm run build && cross-var func extensions install --prefix $npm_package_config_azureFunctions_outDir`
13 verbose stack Exit status 2147516556
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:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid xxx-api#0.0.1
15 verbose cwd C:\Code\xxxAPI\xxx-api
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" "install:extensions"
18 verbose node v12.18.1
19 verbose npm v6.14.5
20 error code ELIFECYCLE
21 error errno 2147516556
22 error xxx-api#0.0.1 install:extensions: `npm run build && cross-var func extensions install --prefix $npm_package_config_azureFunctions_outDir`
22 error Exit status 2147516556
23 error Failed at the xxx-api#0.0.1 install:extensions script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2147516556, true ]

Remove all references of this Marklio dependency from the func.deps.json and run this: npm i -g azure-functions-core-tools#3 --unsafe-perm true

I found that if you go to the path specified after the error message, and delete the Releases folder and run Visual Studio, it will redownload everything you need and it will run fine.

Related

AzureDevOps pipeline - Nightwatch selenium standalone installation issue - Unable to run npm run 'e2e-setup' (contains 'selenium-standalone install')

I am trying to setup selenium standalone server with various browsers the script works fine on my local machine but same has issues working on Azure cloud using Azure DevOps tool.
From the logs (Detailed logs at the end) I see the below but not sure how to fix it:
2020-04-17T21:39:25.3581171Z Usage: selenium-standalone action [options]
2020-04-17T21:39:25.3581533Z
2020-04-17T21:39:25.3582171Z npm ERR! Linux 5.0.0-1031-azure
2020-04-17T21:39:25.3582843Z npm ERR! argv "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node" "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm" "run" "e2e-setup"
2020-04-17T21:39:25.3583217Z npm ERR! node v6.17.1
2020-04-17T21:39:25.3583400Z npm ERR! npm v3.10.10
2020-04-17T21:39:25.3583580Z npm ERR! code ELIFECYCLE
2020-04-17T21:39:25.3584038Z npm ERR! temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3584332Z npm ERR! Exit status 255
I have the below package.json:
{
"name": "temp",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "nightwatch",
"e2e-setup": "selenium-standalone install"
},
"keywords": [],
"author": "",
"license": "ISC",
"devDependencies": {
"#babel/core": "^7.9.0",
"#babel/preset-env": "^7.9.0",
"babel-core": "^6.26.3",
"babel-plugin-add-module-exports": "^1.0.2",
"babel-preset-env": "^1.7.0",
"babel-preset-es2015": "^6.24.1",
"gulp-babel": "^8.0.0-beta.2",
"selenium-standalone": "^6.17.0"
},
"dependencies": {
"easy-soap-request": "^3.2.2",
"nightwatch": "^1.3.4",
"xmldom": "^0.3.0"
}
}
on VScode when I run
npm install nightwatch
npm install selenium-standalone
and
npm run e2e-setup
I do not have any issues when I try the above on my machine - Selenium server jar and all the browser (chrome, firefox, ie, edge) binaries are getting downloaded)
The above setup is as mentioned in the official seleinum-standalone npm website (https://www.npmjs.com/package/selenium-standalone#install--run)
My Azure CI setup:
But when I try the same on Azure DevOps tool (Running the same on Azure cloud) I am having issues like below:
2020-04-17T21:39:22.1913471Z ##[section]Starting: npm run e2e-setup
2020-04-17T21:39:22.1923363Z ==============================================================================
2020-04-17T21:39:22.1923659Z Task : npm
2020-04-17T21:39:22.1924046Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Azure Artifacts.
2020-04-17T21:39:22.1924428Z Version : 1.166.1
2020-04-17T21:39:22.1924652Z Author : Microsoft Corporation
2020-04-17T21:39:22.1924983Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/package/npm
2020-04-17T21:39:22.1925348Z ==============================================================================
2020-04-17T21:39:22.5235427Z SYSTEMVSSCONNECTION exists true
2020-04-17T21:39:22.7105531Z SYSTEMVSSCONNECTION exists true
2020-04-17T21:39:22.7890296Z [command]/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm --version
2020-04-17T21:39:23.0268360Z 3.10.10
2020-04-17T21:39:23.9587311Z [command]/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm config list
2020-04-17T21:39:24.4295571Z ; cli configs
2020-04-17T21:39:24.4297644Z user-agent = "npm/3.10.10 node/v6.17.1 linux x64"
2020-04-17T21:39:24.4298039Z
2020-04-17T21:39:24.4298357Z ; environment configs
2020-04-17T21:39:24.4298785Z userconfig = "/vsts/agent/_work/_temp/npm/830.npmrc"
2020-04-17T21:39:24.4299106Z
2020-04-17T21:39:24.4299481Z ; node bin location = /vsts/agent/_work/_tool/node/6.17.1/x64/bin/node
2020-04-17T21:39:24.4300000Z ; cwd = /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:24.4300385Z ; HOME = /root
2020-04-17T21:39:24.4301230Z ; "npm config ls -l" to show all defaults.
2020-04-17T21:39:24.4301526Z
2020-04-17T21:39:24.4304850Z [command]/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm run e2e-setup
2020-04-17T21:39:25.3579514Z not found: java
2020-04-17T21:39:25.3579860Z
2020-04-17T21:39:25.3581171Z Usage: selenium-standalone action [options]
2020-04-17T21:39:25.3581533Z
2020-04-17T21:39:25.3582171Z npm ERR! Linux 5.0.0-1031-azure
2020-04-17T21:39:25.3582843Z npm ERR! argv "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node" "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm" "run" "e2e-setup"
2020-04-17T21:39:25.3583217Z npm ERR! node v6.17.1
2020-04-17T21:39:25.3583400Z npm ERR! npm v3.10.10
2020-04-17T21:39:25.3583580Z npm ERR! code ELIFECYCLE
2020-04-17T21:39:25.3584038Z npm ERR! temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3584332Z npm ERR! Exit status 255
2020-04-17T21:39:25.3584511Z npm ERR!
2020-04-17T21:39:25.3584965Z npm ERR! Failed at the temp#1.0.0 e2e-setup script 'selenium-standalone install'.
2020-04-17T21:39:25.3585333Z npm ERR! Make sure you have the latest version of node.js and npm installed.
2020-04-17T21:39:25.3585684Z npm ERR! If you do, this is most likely a problem with the temp package,
2020-04-17T21:39:25.3585947Z npm ERR! not with npm itself.
2020-04-17T21:39:25.3586231Z npm ERR! Tell the author that this fails on your system:
2020-04-17T21:39:25.3586678Z npm ERR! selenium-standalone install
2020-04-17T21:39:25.3587020Z npm ERR! You can get information on how to open an issue for this project with:
2020-04-17T21:39:25.3587342Z npm ERR! npm bugs temp
2020-04-17T21:39:25.3587803Z npm ERR! Or if that isn't available, you can get their info via:
2020-04-17T21:39:25.3588109Z npm ERR! npm owner ls temp
2020-04-17T21:39:25.3588351Z npm ERR! There is likely additional logging output above.
2020-04-17T21:39:25.3588530Z
2020-04-17T21:39:25.3588791Z npm ERR! Please include the following file with any support request:
2020-04-17T21:39:25.3589311Z npm ERR! /vsts/agent/_work/r2/a/_QA_IDLookUp/npm-debug.log
2020-04-17T21:39:25.3590596Z > temp#1.0.0 e2e-setup /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:25.3591763Z > selenium-standalone install
2020-04-17T21:39:25.3592087Z
2020-04-17T21:39:25.3734932Z Found npm debug log, make sure the path matches with the one in npm's output: /vsts/agent/_work/r2/a/_QA_IDLookUp/npm-debug.log
2020-04-17T21:39:25.3735698Z 0 info it worked if it ends with ok
2020-04-17T21:39:25.3737184Z 1 verbose cli [ '/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node',
2020-04-17T21:39:25.3738213Z 1 verbose cli '/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm',
2020-04-17T21:39:25.3739010Z 1 verbose cli 'run',
2020-04-17T21:39:25.3739677Z 1 verbose cli 'e2e-setup' ]
2020-04-17T21:39:25.3740072Z 2 info using npm#3.10.10
2020-04-17T21:39:25.3740401Z 3 info using node#v6.17.1
2020-04-17T21:39:25.3741309Z 4 verbose run-script [ 'pree2e-setup', 'e2e-setup', 'poste2e-setup' ]
2020-04-17T21:39:25.3742292Z 5 info lifecycle temp#1.0.0~pree2e-setup: temp#1.0.0
2020-04-17T21:39:25.3743416Z 6 silly lifecycle temp#1.0.0~pree2e-setup: no script for pree2e-setup, continuing
2020-04-17T21:39:25.3744395Z 7 info lifecycle temp#1.0.0~e2e-setup: temp#1.0.0
2020-04-17T21:39:25.3745399Z 8 verbose lifecycle temp#1.0.0~e2e-setup: unsafe-perm in lifecycle true
2020-04-17T21:39:25.3747409Z 9 verbose lifecycle temp#1.0.0~e2e-setup: PATH: /vsts/agent/_work/_tool/node/6.17.1/x64/lib/node_modules/npm/bin/node-gyp-bin:/vsts/agent/_work/r2/a/_QA_IDLookUp/node_modules/.bin:/vsts/agent/_work/_tool/node/6.17.1/x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
2020-04-17T21:39:25.3749200Z 10 verbose lifecycle temp#1.0.0~e2e-setup: CWD: /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:25.3750457Z 11 silly lifecycle temp#1.0.0~e2e-setup: Args: [ '-c', 'selenium-standalone install' ]
2020-04-17T21:39:25.3751608Z 12 silly lifecycle temp#1.0.0~e2e-setup: Returned: code: 255 signal: null
2020-04-17T21:39:25.3752743Z 13 info lifecycle temp#1.0.0~e2e-setup: Failed to exec e2e-setup script
2020-04-17T21:39:25.3753814Z 14 verbose stack Error: temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3754348Z 14 verbose stack Exit status 255
2020-04-17T21:39:25.3755003Z 14 verbose stack at EventEmitter.<anonymous> (/vsts/agent/_work/_tool/node/6.17.1/x64/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
2020-04-17T21:39:25.3755744Z 14 verbose stack at emitTwo (events.js:106:13)
2020-04-17T21:39:25.3756353Z 14 verbose stack at EventEmitter.emit (events.js:191:7)
2020-04-17T21:39:25.3757140Z 14 verbose stack at ChildProcess.<anonymous> (/vsts/agent/_work/_tool/node/6.17.1/x64/lib/node_modules/npm/lib/utils/spawn.js:40:14)
2020-04-17T21:39:25.3757834Z 14 verbose stack at emitTwo (events.js:106:13)
2020-04-17T21:39:25.3758420Z 14 verbose stack at ChildProcess.emit (events.js:191:7)
2020-04-17T21:39:25.3759038Z 14 verbose stack at maybeClose (internal/child_process.js:920:16)
2020-04-17T21:39:25.3759714Z 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
2020-04-17T21:39:25.3760203Z 15 verbose pkgid temp#1.0.0
2020-04-17T21:39:25.3760616Z 16 verbose cwd /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:25.3761457Z 17 error Linux 5.0.0-1031-azure
2020-04-17T21:39:25.3762546Z 18 error argv "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node" "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm" "run" "e2e-setup"
2020-04-17T21:39:25.3763170Z 19 error node v6.17.1
2020-04-17T21:39:25.3763496Z 20 error npm v3.10.10
2020-04-17T21:39:25.3763826Z 21 error code ELIFECYCLE
2020-04-17T21:39:25.3764642Z 22 error temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3765087Z 22 error Exit status 255
2020-04-17T21:39:25.3765921Z 23 error Failed at the temp#1.0.0 e2e-setup script 'selenium-standalone install'.
2020-04-17T21:39:25.3766518Z 23 error Make sure you have the latest version of node.js and npm installed.
2020-04-17T21:39:25.3767106Z 23 error If you do, this is most likely a problem with the temp package,
2020-04-17T21:39:25.3767909Z 23 error not with npm itself.
2020-04-17T21:39:25.3768396Z 23 error Tell the author that this fails on your system:
2020-04-17T21:39:25.3769248Z 23 error selenium-standalone install
2020-04-17T21:39:25.3769864Z 23 error You can get information on how to open an issue for this project with:
2020-04-17T21:39:25.3770358Z 23 error npm bugs temp
2020-04-17T21:39:25.3771224Z 23 error Or if that isn't available, you can get their info via:
2020-04-17T21:39:25.3771966Z 23 error npm owner ls temp
2020-04-17T21:39:25.3772352Z 23 error There is likely additional logging output above.
2020-04-17T21:39:25.3772813Z 24 verbose exit [ 1, true ]
2020-04-17T21:39:25.3773034Z
2020-04-17T21:39:25.3775507Z ##[error]Error: Npm failed with return code: 1
2020-04-17T21:39:25.3816759Z ##[section]Finishing: npm run e2e-setup
The version of node and npm seem to be very old. I have been running nightwatch tests using selenium on travis, azure devops and github actions. My advice is to have the configuration through a yml file which is very simple. You can see mine in the below link and try it.
Reference: https://github.com/spnraju/nightwatchjs-selenium-example/blob/master/azure-pipelines.yml

run start:dev failes Unexpected identifier in concurrently

I'm rather new to the nodejs world and having trouble with some basics ,
when I do npm install it shows a few warn messages but complete it .
when I do npm build it works fine
but when I do run start:dev it crashes with this error message :
concurrently\bin\concurrently.js:140
let lastColor;
^^^^^^^^^
SyntaxError: Unexpected identifier
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start:dev"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! code ELIFECYCLE
npm ERR! izi-backend#0.0.1 start:dev: `concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json" `
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the izi-backend#0.0.1 start:dev script 'concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json" '.
npm ERR! This is most likely a problem with the izi-backend package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json"
npm ERR! You can get their info via:
npm ERR! npm owner ls izi-backend
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\dev\iziMobile\izi-server\npm-debug.log
where npm run start:dev is defined as :
"start:dev": "concurrently --handle-input \"wait-on dist/main.js && nodemon\" \"tsc -w -p tsconfig.build.json\" "
also printing out npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files (x86)\nodejs\\node.exe',
1 verbose cli 'C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start:dev' ]
2 info using npm#2.7.4
3 info using node#v0.12.2
4 verbose node symlink C:\Program Files (x86)\nodejs\node.exe
5 verbose run-script [ 'prestart:dev', 'start:dev', 'poststart:dev' ]
6 info prestart:dev izi-backend#0.0.1
7 info start:dev izi-backend#0.0.1
8 verbose unsafe-perm in lifecycle true
9 info izi-backend#0.0.1 Failed to exec start:dev script
10 verbose stack Error: izi-backend#0.0.1 start:dev: concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json"
10 verbose stack Exit status 1
10 verbose stack at EventEmitter. (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\lifecycle.js:213:16)
10 verbose stack at EventEmitter.emit (events.js:110:17)
10 verbose stack at ChildProcess. (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\spawn.js:14:12)
10 verbose stack at ChildProcess.emit (events.js:110:17)
10 verbose stack at maybeClose (child_process.js:1015:16)
10 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
11 verbose pkgid izi-backend#0.0.1
12 verbose cwd C:\dev\iziMobile\izi-server
13 error Windows_NT 6.3.9600
14 error argv "C:\Program Files (x86)\nodejs\\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "run" "start:dev"
15 error node v0.12.2
16 error npm v2.7.4
17 error code ELIFECYCLE
18 error izi-backend#0.0.1 start:dev: concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json"
18 error Exit status 1
19 error Failed at the izi-backend#0.0.1 start:dev script 'concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json" '.
19 error This is most likely a problem with the izi-backend package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error concurrently --handle-input "wait-on dist/main.js && nodemon" "tsc -w -p tsconfig.build.json"
19 error You can get their info via:
19 error npm owner ls izi-backend
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]<
Concurrently is a package I take in packages.json so I doubt there is really an error there...
Am I missing anything ?
Any help will do at this point
Node v0.12.2 does not support the let declarations.
See here for the full version support matrix.
You are using node version v0.12.2. let syntax is not supported.
From node.green you can see that let is supported from Node v6.4.x

brunch build --production fails only in production

Out of the blue build script started to fail. No changes in environment or configs at all. Works fine in dev, fails in prod.
Both dev and prod (both Ubuntus):
$ npm -v
5.3.0
$ node -v
v6.11.2
In dev:
oleg#DevVM ~/Code/loaded.bike/assets $ npm run deploy
> # deploy /home/oleg/Code/loaded.bike/assets
> brunch build --production
17:49:59 - info: compiling
17:49:59 - info: compiled 19 files into 2 files, copied 32 in 6.9 sec
In prod:
deploy#loaded-bike-app:~/builds/assets$ npm run deploy
> # deploy /home/deploy/builds/assets
> brunch build --production
00:45:30 - error: Initialization error - Could not load global module 'jquery'. Possible solution: add 'jquery' to package.json and `npm install`. Could not load global module 'jquery'. Possible solution: add 'jquery' to package.json and `npm install`.
Stack trace was suppressed. Run with `LOGGY_STACKS=1` to see the trace.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # deploy: `brunch build --production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # deploy 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/deploy/.npm/_logs/2017-08-12T00_45_30_084Z-debug.log
Full log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'deploy' ]
2 info using npm#5.3.0
3 info using node#v6.11.2
4 verbose run-script [ 'predeploy', 'deploy', 'postdeploy' ]
5 info lifecycle #~predeploy: #
6 info lifecycle #~deploy: #
7 verbose lifecycle #~deploy: unsafe-perm in lifecycle true
8 verbose lifecycle #~deploy: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/deploy/builds/assets/node_modules/.bin:/home/deploy/bin:/home/deploy/.local
/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle #~deploy: CWD: /home/deploy/builds/assets
10 silly lifecycle #~deploy: Args: [ '-c', 'brunch build --production' ]
11 silly lifecycle #~deploy: Returned: code: 1 signal: null
12 info lifecycle #~deploy: Failed to exec deploy script
13 verbose stack Error: # deploy: `brunch build --production`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at EventEmitter.emit (events.js:191:7)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at ChildProcess.emit (events.js:191:7)
13 verbose stack at maybeClose (internal/child_process.js:891:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
14 verbose pkgid #
15 verbose cwd /home/deploy/builds/assets
16 verbose Linux 4.8.0-41-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "deploy"
18 verbose node v6.11.2
19 verbose npm v5.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error # deploy: `brunch build --production`
22 error Exit status 1
23 error Failed at the # deploy script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Adding jquery, tether to package.json fixes require error but then it just chokes on sass compile. Is this just JS missfiring async function out of order or what is going here? Once again, it started to fail completely out of the blue. Deployed just fine yesterday and today if fails without me changing anything. Any clue what might be wrong here?
EDIT:
package.json:
{
"repository": {},
"license": "MIT",
"scripts": {
"deploy": "brunch build --production",
"watch": "brunch watch --stdin"
},
"dependencies": {
"bootstrap": "^4.0.0-alpha.6",
"phoenix": "file:../deps/phoenix",
"phoenix_html": "file:../deps/phoenix_html"
},
"devDependencies": {
"babel-brunch": "6.0.6",
"brunch": "2.10.10",
"clean-css-brunch": "2.10.0",
"css-brunch": "2.10.0",
"sass-brunch": "2.10.4",
"uglify-js-brunch": "2.1.1"
}
}
I'm actually seeing this crap on prod (but not on dev)
npm ERR! peer dep missing: jquery#>=3.0.0, required by bootstrap#4.0.0-beta
npm ERR! peer dep missing: popper.js#^1.11.0, required by bootstrap#4.0.0-beta
What is that about? Bootstrap defines those as dependencies (not peerDependency) in its own package.json. npm doesn't pull in dependencies now?
"bootstrap": "^4.0.0-alpha.6"
Needed to lock the version. Bootstrap went from alpha.6 to beta yesterday. Messed everything up. No idea why is started to fail only on one machine (even after npm cache clear). Sass compile fails under beta, so I locked it to alpha.6 for now.
I think I need to start locking dependency versions. This took way too long to figure out.

Why is Windows 10 attempting to find this node module from Apache Zeppelin in C:/ instead of the local directory?

I am using Apache Zeppelin 0.8.0 to create some software for data visualization. Specifically, I am using the Helium plugin system that Zeppelin provides to create some sharp charts and graphs from High Charts. Using Linux and Mac, I have had no issues getting the visualizations to run-- including the advanced visualizations provided by zeppelin, but they do not work on windows 10 properly. You can test it by downloading the binary package provided by zeppelin on their home page, install it, run it and then go to the Helium area in the menu-- you will notice the advanced visualizations do not appear (windows 10).
The main issue is with nodejs-- it is trying to find the node module for a package at C:\ instead of the directory where it is being run from-- here is the output:
Running 'npm run bundle --registry=http://registry.npmjs.org/' in C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle
> zeppelin-helium-bundle# bundle C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle
> node/node node_modules/webpack/bin/webpack.js --display-error-details --json
module.js:471
throw err;
^
Error: Cannot find module 'C:\node'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Users\\Pablo\\Desktop\\zeppelin-0.8.0-SNAPSHOT\\local-repo\\helium-bundle\\node\\node.exe" "C:\\Users\\Pablo\\Desktop\\zeppelin-0.8.0-SNAPSHOT\\local-repo\\helium-bundle\\node\\node_modules\\npm\\bin\\npm-cli.js" "run" "bundle" "--registry=http://registry.npmjs.org/"
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! zeppelin-helium-bundle# bundle: `node/node node_modules/webpack/bin/webpack.js --display-error-details --json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zeppelin-helium-bundle# bundle script 'node/node node_modules/webpack/bin/webpack.js --display-error-details --json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the zeppelin-helium-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node/node node_modules/webpack/bin/webpack.js --display-error-details --json
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs zeppelin-helium-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls zeppelin-helium-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle\npm-debug.log
And here is the npm-debug.log file:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Users\\Pablo\\Desktop\\zeppelin-0.8.0-SNAPSHOT\\local-repo\\helium-bundle\\node\\node.exe',
1 verbose cli 'C:\\Users\\Pablo\\Desktop\\zeppelin-0.8.0-SNAPSHOT\\local-repo\\helium-bundle\\node\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'bundle',
1 verbose cli '--registry=http://registry.npmjs.org/' ]
2 info using npm#3.10.8
3 info using node#v6.9.1
4 verbose run-script [ 'prebundle', 'bundle', 'postbundle' ]
5 info lifecycle zeppelin-helium-bundle#~prebundle: zeppelin-helium-bundle#
6 silly lifecycle zeppelin-helium-bundle#~prebundle: no script for prebundle, continuing
7 info lifecycle zeppelin-helium-bundle#~bundle: zeppelin-helium-bundle#
8 verbose lifecycle zeppelin-helium-bundle#~bundle: unsafe-perm in lifecycle true
9 verbose lifecycle zeppelin-helium-bundle#~bundle: PATH: C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle\node\node_modules\npm\bin\node-gyp-bin;C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle\node_modules\.bin;C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle\node;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files (x86)\scala\bin;C:\Users\Pablo\AppData\Roaming\npm;C:\nodejs;C:\Users\Pablo\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Heroku\bin;C:\Users\Pablo\AppData\Roaming\npm;C:\nodejs;
10 verbose lifecycle zeppelin-helium-bundle#~bundle: CWD: C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle
11 silly lifecycle zeppelin-helium-bundle#~bundle: Args: [ '/d /s /c',
11 silly lifecycle 'node/node node_modules/webpack/bin/webpack.js --display-error-details --json' ]
12 silly lifecycle zeppelin-helium-bundle#~bundle: Returned: code: 1 signal: null
13 info lifecycle zeppelin-helium-bundle#~bundle: Failed to exec bundle script
14 verbose stack Error: zeppelin-helium-bundle# bundle: `node/node node_modules/webpack/bin/webpack.js --display-error-details --json`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle\node\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle\node\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid zeppelin-helium-bundle#
16 verbose cwd C:\Users\Pablo\Desktop\zeppelin-0.8.0-SNAPSHOT\local-repo\helium-bundle
17 error Windows_NT 10.0.14393
18 error argv "C:\\Users\\Pablo\\Desktop\\zeppelin-0.8.0-SNAPSHOT\\local-repo\\helium-bundle\\node\\node.exe" "C:\\Users\\Pablo\\Desktop\\zeppelin-0.8.0-SNAPSHOT\\local-repo\\helium-bundle\\node\\node_modules\\npm\\bin\\npm-cli.js" "run" "bundle" "--registry=http://registry.npmjs.org/"
19 error node v6.9.1
20 error npm v3.10.8
21 error code ELIFECYCLE
22 error zeppelin-helium-bundle# bundle: `node/node node_modules/webpack/bin/webpack.js --display-error-details --json`
22 error Exit status 1
23 error Failed at the zeppelin-helium-bundle# bundle script 'node/node node_modules/webpack/bin/webpack.js --display-error-details --json'.
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 zeppelin-helium-bundle package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node/node node_modules/webpack/bin/webpack.js --display-error-details --json
23 error You can get information on how to open an issue for this project with:
23 error npm bugs zeppelin-helium-bundle
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls zeppelin-helium-bundle
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
I have searched extensively and have attempted reinstalling nodejs on my current system, as well as updating environmental variables. Currently, my theory is that there is an Autorun string somewhere on my machine that is causing it to automatically run/search for this package in C:/, but it is a wild theory. Any help would be greatly appreciated. Here is a screenshot of my zeppelin helium package page:
Helium - Zeppelin Windows 10 Issues

NODE_PATH throws error when NPM starts on windows 10

I am trying to built a MEAN Todo app by following https://github.com/michaelcheng429/super-mean-stack
package.json
{
"name": "ToDoThoughts",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"start": "NODE_PATH=$NODE_PATH:./app node server",
"dev": "npm start & webpack-dev-server --progress --colors"
},
"license": "ISC",
"dependencies": {
"angular": "1.4.12",
"angular-ui-router": "0.3.1",
"body-parser": "1.15.2",
"bootstrap": "3.3.7",
"express": "4.14.0"
},
"devDependencies": {
"babel-core": "6.17.0",
"babel-preset-es2015": "6.16.0",
"raw-loader": "0.5.1",
"webpack": "1.13.2",
"webpack-dev-server": "1.16.2"
},
"engines": {
"node": "5.5.0"
}
}
I am getting error when i run the command "npm run dev" in the command prompt.
I have also attached npm.debug.log
> ToDoThoughts#1.0.0 start C:\Projects\ToDoThoughts
> NODE_PATH=$NODE_PATH:./app node server
'NODE_PATH' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Selva\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v6.5.0
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! ToDoThoughts#1.0.0 start: `NODE_PATH=$NODE_PATH:./app node server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ToDoThoughts#1.0.0 start script 'NODE_PATH=$NODE_PATH:./app node server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ToDoThoughts package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_PATH=$NODE_PATH:./app node server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs ToDoThoughts
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls ToDoThoughts
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Projects\ToDoThoughts\npm-debug.log
npm.debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\Selva\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#3.10.8
3 info using node#v6.5.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle ToDoThoughts#1.0.0~prestart: ToDoThoughts#1.0.0
6 silly lifecycle ToDoThoughts#1.0.0~prestart: no script for prestart, continuing
7 info lifecycle ToDoThoughts#1.0.0~start: ToDoThoughts#1.0.0
8 verbose lifecycle ToDoThoughts#1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle ToDoThoughts#1.0.0~start: PATH: C:\Users\Selva\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Projects\ToDoThoughts\node_modules\.bin;C:\Users\Selva\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Projects\ToDoThoughts\node_modules\.bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Skype\Phone\;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\Selva\AppData\Local\Microsoft\WindowsApps;C:\Users\Selva\AppData\Roaming\npm;C:\Users\Selva\AppData\Local\atom\bin;C:\Program Files\Git\bin;C:\Projects\ToDoThoughts
10 verbose lifecycle ToDoThoughts#1.0.0~start: CWD: C:\Projects\ToDoThoughts
11 silly lifecycle ToDoThoughts#1.0.0~start: Args: [ '/d /s /c', 'NODE_PATH=$NODE_PATH:./app node server' ]
12 silly lifecycle ToDoThoughts#1.0.0~start: Returned: code: 1 signal: null
13 info lifecycle ToDoThoughts#1.0.0~start: Failed to exec start script
14 verbose stack Error: ToDoThoughts#1.0.0 start: `NODE_PATH=$NODE_PATH:./app node server`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (C:\Users\Selva\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (C:\Users\Selva\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid ToDoThoughts#1.0.0
16 verbose cwd C:\Projects\ToDoThoughts
17 error Windows_NT 10.0.14393
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Selva\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 error node v6.5.0
20 error npm v3.10.8
21 error code ELIFECYCLE
22 error ToDoThoughts#1.0.0 start: `NODE_PATH=$NODE_PATH:./app node server`
22 error Exit status 1
23 error Failed at the ToDoThoughts#1.0.0 start script 'NODE_PATH=$NODE_PATH:./app node server'.
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 ToDoThoughts package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error NODE_PATH=$NODE_PATH:./app node server
23 error You can get information on how to open an issue for this project with:
23 error npm bugs ToDoThoughts
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls ToDoThoughts
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
NPM scripts are executed in the shell from which NPM was invoked.
NODE_PATH=$NODE_PATH:./app node server will not behave correctly if you're using the command prompt or Powershell on Windows. If you already have Git installed, then you should use Git Bash which should already be available.
Otherwise, you might install the MSYS' or Cygwin's Bash shell.
Node on installation should be installed in your systems environment variables and should be called using node in PowerShell or cmd.
This should mean there's no need to always insert the node path in your environment variables.
Make sure you're running PowerShell or cmd as administrator as well, this ensure system environment variables are being picked up.
Lastly, in your package.json change to:
"scripts": {
"start": "node server.js",
"dev": "start cmd /k \"webpack-dev-server --progress --colors\" & node server.js"
}
then run npm start and your server should be running.
"scripts": {
"start": "node server.js",
"dev": "start cmd /k \"webpack-dev-server --progress --colors\" & node server.js"
}
npm cache clean
Then clear package-lock.json file

Resources