Can't update npm - npm ERR! Cannot find module 'update-notifier' - node.js

I can't do npm install on Windows in my application in Angular 8, because I get error:
C:\Repository\Tools\Tools\ClientApp>npm install
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'update-notifier'
npm ERR! Require stack:
npm ERR! - C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xxx\AppData\Roaming\npm-cache\_logs\2021-02-19T13_09_42_358Z-debug.log
in log file:
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:\\Users\\xxx\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install'
1 verbose cli ]
2 info using npm#6.14.11
3 info using node#v14.15.5
4 verbose stack Error: Cannot find module 'update-notifier'
4 verbose stack Require stack:
4 verbose stack - C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
4 verbose stack at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
4 verbose stack at Function.Module._load (internal/modules/cjs/loader.js:725:27)
4 verbose stack at Module.require (internal/modules/cjs/loader.js:952:19)
4 verbose stack at require (internal/modules/cjs/helpers.js:88:18)
4 verbose stack at EventEmitter.<anonymous> (C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js:87:22)
4 verbose stack at processTicksAndRejections (internal/process/task_queues.js:75:11)
5 verbose cwd C:\Repository\Tools.xxx\Tools.xxx\ClientApp
6 verbose Windows_NT 10.0.17763
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\xxx\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
8 verbose node v14.15.5
9 verbose npm v6.14.11
10 error code MODULE_NOT_FOUND
11 error Cannot find module 'update-notifier'
11 error Require stack:
11 error - C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
12 verbose exit [ 1, true ]
Any other command that I try to call causes the same result, for example:
npm i -g npm-upgrade
npm cache clean
npm install -g update-notifier
Error occured when I try to update npm to version 7. Now I uninstall version 7 and there is version 6.14.11 as it was at the begin, but I still can't call npm install
I uninstalled Node.js and installed again but didn't help
In folder:
C:\Users\xxx\AppData\Roaming\npm\node_modules\npm
I have package.json file and inside this file:
"bin": {
"npm": "./bin/npm-cli.js",
"npx": "./bin/npx-cli.js"
},
"dependencies": {
"update-notifier": "^2.5.0",
I tried to remove this line but result is the same, cannot find module update-notifier

I found solution in this question:
npm-cli-js-not-found
Copy the directory named npm from your installed node path (In my case the npm directory was available in C:\Program Files\nodejs\node_modules).
Navigate to C:\Users\%USERNAME%\AppData\Roaming\npm\node_modules and paste the copied npm directory there.

Related

Symfony 5.2 + Webpack Encore: npm run shows error 'Unexpected token'

I have setup a new Symfony 5.2 project and added Webpack Encore on a shared Server with no root access.
Yarn is not available on this machine, so I used npm:
// setup new Symfony 5.2 project
symfony new sym5 --version=5.2 --full
...
cd sym5
// add Webpack Encore
composer require symfony/webpack-encore-bundle
npm install
...
// try to compile assets
npm run dev
I have made no changes to the webpack.config.js and asset/ files which have been automatically created. Running npm run dev leads to an Unexpected token error:
npm run dev
> # dev /customers/123/webpages/sym5
> encore dev
/customers/123/webpages/sym5/node_modules/pkg-up/index.js:4
module.exports = async ({cwd} = {}) => findUp('package.json', {cwd});
^
SyntaxError: Unexpected token (
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/customers/123/webpages/sym5/node_modules/#symfony/webpack-encore/lib/config/parse-runtime.js:13:15)
npm ERR! Linux 3.18.117-pvops-xen-x64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
npm ERR! node v6.11.3
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! # dev: `encore dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # dev script 'encore dev'.
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 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! encore dev
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /customers/123/webpages/sym5/npm-debug.log
Since the error is not reported in any my custom files, I assume that this is a problem of Node.js / Webpack itself? Is this correct?
The message says, that one should use the latest versions of node.js and npm. The versions available on the server (node v6.11.3 and npm v3.10.10) are indeed quite old but without root access I cannot change this, can I?
However, since the adding / installing Webpack Encore using these node.js and npm version worked without any problem, I wonder if using these old version is really the cause of the problem.
Is there anything I can do to find the actual cause and to solve the problem?
// /customers/123/webpages/sym5/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
2 info using npm#3.10.10
3 info using node#v6.11.3
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle #~predev: #
6 silly lifecycle #~predev: no script for predev, continuing
7 info lifecycle #~dev: #
8 verbose lifecycle #~dev: unsafe-perm in lifecycle true
9 verbose lifecycle #~dev: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/customers/123/webpages/sym5/node_modules/.bin:/customers/123/bin/:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/customers/123/.gem/bin
10 verbose lifecycle #~dev: CWD: /customers/123/webpages/sym5
11 silly lifecycle #~dev: Args: [ '-c', 'encore dev' ]
12 silly lifecycle #~dev: Returned: code: 1 signal: null
13 info lifecycle #~dev: Failed to exec dev script
14 verbose stack Error: # dev: `encore dev`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/lib/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> (/usr/lib/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:920:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid #
16 verbose cwd /customers/123/webpages/sym5
17 error Linux 3.18.117-pvops-xen-x64
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
19 error node v6.11.3
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error # dev: `encore dev`
22 error Exit status 1
23 error Failed at the # dev script 'encore dev'.
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 package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error encore dev
23 error You can get information on how to open an issue for this project with:
23 error npm bugs
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Getting started with NPM

I'm trying to get started with ReactJS on an existing project. I'm following instructions here to install NodeJS and Babel, but failing at the second step.
I have installed NodeJS on Windows, correctly as far as I can tell. I've navigated my terminal to the root folder of my Flask app and typed npm init -y. This generates a package.json file in the root of my app. I think this is correct so far.
However, when I try to run the next command in the instructions npm install babel-cli#6 babel-preset-react-app#3 I receive the following error:
(venv) PS C:\Users\Rob\Dropbox\Andon\andon> npm install babel-cli#6 babel-preset-react-app#3
npm ERR! code MODULE_NOT_FOUND
npm ERR! path C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\yallist\package.json
npm ERR! Cannot find module 'C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\yallist\yallist.js'. Please verify that the package.json has a valid "main" entry
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Rob\AppData\Roaming\npm-cache\_logs\2020-04-20T12_55_30_568Z-debug.log
In fact, I receive that error when I try to run any npm install commands. I assume there is some problem with how I've setup NPM, but this is my first time using it and I have no idea.
Any help would be appreciated, please.
EDIT: This is the full log of the error:
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 'install',
1 verbose cli 'babel-cli#6',
1 verbose cli 'babel-preset-react-app#3'
1 verbose cli ]
2 info using npm#6.14.4
3 info using node#v12.16.2
4 verbose stack Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\yallist\yallist.js'. Please verify that the package.json has a valid "main" entry
4 verbose stack at tryPackage (internal/modules/cjs/loader.js:319:19)
4 verbose stack at Function.Module._findPath (internal/modules/cjs/loader.js:703:18)
4 verbose stack at Function.Module._resolveFilename (internal/modules/cjs/loader.js:967:27)
4 verbose stack at Function.Module._load (internal/modules/cjs/loader.js:862:27)
4 verbose stack at Module.require (internal/modules/cjs/loader.js:1042:19)
4 verbose stack at require (internal/modules/cjs/helpers.js:77:18)
4 verbose stack at Object.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\minipass\index.js:3:17)
4 verbose stack at Module._compile (internal/modules/cjs/loader.js:1156:30)
4 verbose stack at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
4 verbose stack at Module.load (internal/modules/cjs/loader.js:1000:32)
4 verbose stack at Function.Module._load (internal/modules/cjs/loader.js:899:14)
4 verbose stack at Module.require (internal/modules/cjs/loader.js:1042:19)
4 verbose stack at require (internal/modules/cjs/helpers.js:77:18)
4 verbose stack at Object.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\lib\extract-stream.js:3:18)
4 verbose stack at Module._compile (internal/modules/cjs/loader.js:1156:30)
4 verbose stack at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
5 verbose cwd C:\Users\Rob\Dropbox\Andon\andon
6 verbose Windows_NT 10.0.18362
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "babel-cli#6" "babel-preset-react-app#3"
8 verbose node v12.16.2
9 verbose npm v6.14.4
10 error code MODULE_NOT_FOUND
11 error path C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\yallist\package.json
12 error Cannot find module 'C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\yallist\yallist.js'. Please verify that the package.json has a valid "main" entry
13 verbose exit [ 1, true ]
Sometimes such problems are related to the fact Node is installed in a path with spaces ( ie "Program Files" ) try to install somewhere else in a folder without spaces.

npm ERR! Cannot find module 'spdx-expression-parse'

This error occurred while command npm run watch was in process, I tried to solve it with different tactics but can't find any solution
Steps which I tried to resolve the issue
1) Remove node module, package-lock.json, yarn.lock npm cache clear and the run npm install but error still occurs.
2) Remove nodejs from control panel and reinstall with latest and then old/previous version and the reinstall but can't succeed, error still occurs.
npm ERR! code MODULE_NOT_FOUND npm ERR! Cannot find module
'spdx-expression-parse'
npm ERR! A complete log of this run can be found in: npm ERR!
C:\Users\DELL\AppData\Roaming\npm-cache_logs\2018-12-20T08_00_01_749Z-debug.log
Log File
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\DELL\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install' ]
2 info using npm#6.5.0
3 info using node#v8.12.0
4 verbose stack Error: Cannot find module 'spdx-expression-parse'
4 verbose stack at Function.Module._resolveFilename (module.js:548:15)
4 verbose stack at Function.Module._load (module.js:475:25)
4 verbose stack at Module.require (module.js:597:17)
4 verbose stack at require (internal/module.js:11:18)
4 verbose stack at Object.<anonymous> (C:\Users\DELL\AppData\Roaming\npm\node_modules\npm\node_modules\validate-npm-package-license\index.js:1:75)
4 verbose stack at Module._compile (module.js:653:30)
4 verbose stack at Object.Module._extensions..js (module.js:664:10)
4 verbose stack at Module.load (module.js:566:32)
4 verbose stack at tryModuleLoad (module.js:506:12)
4 verbose stack at Function.Module._load (module.js:498:3)
5 verbose cwd D:\it-88-lynx
6 verbose Windows_NT 10.0.17134
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\DELL\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
8 verbose node v8.12.0
9 verbose npm v6.5.0
10 error code MODULE_NOT_FOUND
11 error Cannot find module 'spdx-expression-parse'
12 verbose exit [ 1, true ]
Atlast, I have solved the problem, the spdx-expression-parse has been corrupted located in users/AppData/Roaming/npm/node_modules/
remove node_modules
uninstall nodejs
(Start Main Step)
Go to users/AppData/Roaming and delete npm and npm-cache folders manually
(End Main Step)
then run following command
rm -rf node_modules
rm package-lock.json yarn.lock
npm cache clear --force
npm install
thanks for all your suppport.

react-native node dependency install broke project

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

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

Resources