Issue with CLI Windows installer, emit of null

I’m running into issues trying to use particle setup from a fresh install of the Windows CLI. At this point I have done some troubleshooting by switching node versions, uninstalling the CLI, trying to install it from npm, etc. I have looked through the other posts with CLI issues and mine does not seem to match any I’ve found.

I have done a clean install removing everything I was testing with before and did a fresh install with the Windows CLI Installer:

Here is my current error report:

 C:\WINDOWS\system32>particle setup
particle: Installing plugins (retrying)...
 !    Error installing package.
 !    npm WARN excluding symbolic link test\server\static\ie8-polyfill.js -> ../../../ie8-polyfill.js
 !    npm ERR! Windows_NT 10.0.17134
 !    npm ERR! argv "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\bin\\node.exe" "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\lib\\node_modules\\npm\\cli.js" "install" "particle-cli"
 !    npm ERR! node v5.4.1
 !    npm ERR! npm  v3.3.10
 !
 !    npm ERR! Cannot read property 'emit' of null
 !    npm ERR!
 !    npm ERR! If you need help, you may report this error at:
 !    npm ERR!     <https://github.com/npm/npm/issues>
 !    npm ERR! Windows_NT 10.0.17134
 !    npm ERR! argv "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\bin\\node.exe" "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\lib\\node_modules\\npm\\cli.js" "install" "particle-cli"
 !    npm ERR! node v5.4.1
 !    npm ERR! npm  v3.3.10
 !
 !    npm ERR! Cannot read property 'emit' of null
 !    npm ERR!
 !    npm ERR! If you need help, you may report this error at:
 !    npm ERR!     <https://github.com/npm/npm/issues>
 !    npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
 !    npm ERR! Windows_NT 10.0.17134
 !    npm ERR! argv "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\bin\\node.exe" "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\lib\\node_modules\\npm\\cli.js" "install" "particle-cli"
 !    npm ERR! node v5.4.1
 !    npm ERR! npm  v3.3.10
 !
 !    npm ERR! Cannot read property 'emit' of null
 !    npm ERR!
 !    npm ERR! If you need help, you may report this error at:
 !    npm ERR!     <https://github.com/npm/npm/issues>
 !    npm ERR! Windows_NT 10.0.17134
 !    npm ERR! argv "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\bin\\node.exe" "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\lib\\node_modules\\npm\\cli.js" "install" "particle-cli"
 !    npm ERR! node v5.4.1
 !    npm ERR! npm  v3.3.10
 !
 !    npm ERR! Cannot read property 'emit' of null
 !    npm ERR!
 !    npm ERR! If you need help, you may report this error at:
 !    npm ERR!     <https://github.com/npm/npm/issues>
 !    npm WARN deprecated hoek@2.16.3: The major version is no longer supported. Please update to 4.x or newer
 !    npm WARN deprecated parser-byte-length@1.0.2: renamed to @serialport/parser-byte-length
 !    npm WARN deprecated parser-cctalk@1.0.2: reanmed to @serialport/parser-cctalk
 !    npm WARN deprecated parser-regex@1.0.2: reanmed to @serialport/parser-regex
 !    npm WARN deprecated parser-delimiter@1.0.2: reanmed to @serialport/parser-delimiter
 !    npm WARN deprecated parser-ready@1.0.2: reanmed to @serialport/parser-ready
 !    npm WARN deprecated parser-readline@1.0.2: reanmed to @serialport/parser-readline
 !    npm WARN engine clone-deep@4.0.0: wanted: {"node":">=8"} (current: {"node":"5.4.1","npm":"3.3.10"})
 !    npm WARN engine set-value@3.0.0: wanted: {"node":">=6.0"} (current: {"node":"5.4.1","npm":"3.3.10"})
 !    npm WARN engine shallow-clone@3.0.0: wanted: {"node":">=8"} (current: {"node":"5.4.1","npm":"3.3.10"})
 !    npm ERR! Windows_NT 10.0.17134
 !    npm ERR! argv "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\bin\\node.exe" "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\lib\\node_modules\\npm\\cli.js" "install" "particle-cli"
 !    npm ERR! node v5.4.1
 !    npm ERR! npm  v3.3.10
 !
 !    npm ERR! Cannot read property 'emit' of null
 !    npm ERR!
 !    npm ERR! If you need help, you may report this error at:
 !    npm ERR!     <https://github.com/npm/npm/issues>
 !    npm WARN excluding symbolic link test\server\static\ie8-polyfill.js -> ../../../ie8-polyfill.js
 !    npm WARN ENOENT ENOENT: no such file or directory, open 'C:\Users\Andrew\AppData\Local\particle\package.json'
 !    npm WARN EPACKAGEJSON particle No description
 !    npm WARN EPACKAGEJSON particle No repository field.
 !    npm WARN EPACKAGEJSON particle No README data
 !    npm WARN EPACKAGEJSON particle No license field.
 !    npm ERR! Windows_NT 10.0.17134
 !    npm ERR! argv "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\bin\\node.exe" "C:\\Users\\Andrew\\AppData\\Local\\particle\\node-v5.4.1-windows-x64\\lib\\node_modules\\npm\\cli.js" "install" "particle-cli"
 !    npm ERR! node v5.4.1
 !    npm ERR! npm  v3.3.10
 !
 !    npm ERR! Callback called more than once.
 !    npm ERR!
 !    npm ERR! If you need help, you may report this error at:
 !    npm ERR!     <https://github.com/npm/npm/issues>
 !
 !    npm ERR! Please include the following file with any support request:
 !    npm ERR!     C:\Users\Andrew\AppData\Local\particle\npm-debug.log
 !
 !    Try running again with GODE_DEBUG=info to see more output.

I am scratching my head at this point. Is it related to the version of node being distributed with the CLI? v5.4.1 is pretty old and I did have a slightly different error when I was using v8.11.4, but v5.4.1 was still being shown in the log.

Update: I was able to get this working just fine on my laptop, so the issue seems to be isolated to my desktop. I will add another update if I am able to figure this out.

2 Likes

Thank you for the update! Let us know if you run into any more problems.

So to round this all out it seems today that I was able to install the CLI again and it is working fine. I made sure to right click and run as admin this time and it works just fine now. I am not sure why the UAC prompt that occurs without right clicking was not enough the first few times but it is working now.

Anyone running into a similar issue make sure to try right clicking and run as admin.