Are there any other options I have available to salvage the device outside of reinstalling my OS? Is there not a “non-cloud-based” solution for getting my core up and running? It’s pretty frustrating that I’m forced to use the cloud, but things only work about 80% of the time. Unacceptable.
which nodejs /usr/bin/nodejs nodejs -v v0.10.25 npm -v 1.4.21 sudo npm install -g particle-cli \ > firstname.lastname@example.org install /usr/local/lib/node_modules/particle-cli/node_modules/serialport > node-pre-gyp install --fallback-to-build /usr/bin/env: node: No such file or directory npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian npm ERR! email@example.com install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 127 npm ERR! npm ERR! Failed at the firstname.lastname@example.org install script. npm ERR! This is most likely a problem with the serialport package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build npm ERR! You can get their info via: npm ERR! npm owner ls serialport npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.19.0-18-generic npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "particle-cli" npm ERR! cwd /home/brad npm ERR! node -v v0.10.25 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/brad/npm-debug.log npm ERR! not ok code 0