- Code: Select all
/opt/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:35
throw ex;
^
Error: The module '/opt/local/lib/node_modules/homebridge/node_modules/mdns/build/Release/dns_sd_bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 48. This version of Node.js requires
NODE_MODULE_VERSION 51. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or`npm install`).
at Object.Module._extensions..node (module.js:598:18)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/opt/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:24:20)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
I wonder if someone who knows what's up with npm could point to some sort of an article regarding best practices for keeping this from happening--or even marginal practices to enable the unwashed to keep homeBridge running when NODE_WHATSIS_VERSION ∞ changes to VERSION ∞.1
Because now I've tried "npm install homebridge" and "npm install homebridge-indigo" and "npm rebuild homebridge" and "npm rebuild homebridge-indigo" and "npm rebuild" and the Home app still says "65 accessories not responding."
Along the way I get a nice peppering of
- Code: Select all
npm WARN enoent ENOENT: no such file or directory, open '/Users/mike/package.json'
npm WARN mike No description
npm WARN mike No repository field.
npm WARN mike No README data
npm WARN mike No license field.