Can not install npm tessel (1) on OS X 10.11.1 and node v4.2.1

s7nio 2015-10-28 20:11:42 UTC #1

Hi, I've reinstall my mac and and (re)headed up to tessel.io/start

After the node installation via (home)brew and npm install -g tessel i got the following log...

gist.github.com

https://gist.github.com/s7nio/2cc0359585223e070251

npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/4.2.1/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   'tessel' ]
2 info using npm@2.14.7
3 info using node@v4.2.1
4 verbose install initial load of /usr/local/lib/package.json
5 verbose readDependencies loading dependencies from /usr/local/lib/package.json

This file has been truncated. show original

s7nio 2015-10-28 20:18:41 UTC #2

I've fix it. Uninstall the current node version and install the latest node 0.12.x (0.12.7).
$ brew uninstall node
$ brew install homebrew/versions/node012

Kelsey 2015-10-31 14:24:31 UTC #3

Sorry for the slow response & thanks for posting your fix! I've made an issue for this here.

Logan 2015-11-09 15:06:09 UTC #4

There's also some really fun output on my machine when running Node v5.0. This happens immediately after attempting a tessel run ...

module.js:450
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: Module version mismatch. Expected 47, got 14.
    at Error (native)
    at Object.Module._extensions..node (module.js:450:18)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/tessel/node_modules/usb/usb.js:5:38)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)

I've since downgraded using brew back to 12.7 and all is good in Tessel land.

jon 2015-11-09 21:16:42 UTC #5

@Logan I've seen that happen when you switch Node versions without re-running npm install. Binary dependencies are linked to specific Node versions and throw a tantrum if the Node version that's running them doesn't match what compiled them.

-Jon