question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong node version

See original GitHub issue

I get this error as soon as I try to run homebridge. I tried to reinstall both dns and homebridge using “npm install -g” but that didn’t make a difference:

/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:35 throw ex; ^

Error: The module ‘/usr/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 57. This version of Node.js requires NODE_MODULE_VERSION 59. Please try re-compiling or re-installing the module (for instance, using npm rebuild or npm install). at Object.Module._extensions…node (module.js:689:18) at Module.load (module.js:573:32) at tryModuleLoad (module.js:513:12) at Function.Module._load (module.js:505:3) at Module.require (module.js:604:17) at require (internal/module.js:11:18) at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/dns_sd.js:24:20) at Module._compile (module.js:660:30) at Object.Module._extensions…js (module.js:671:10) at Module.load (module.js:573:32)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:10 (1 by maintainers)

github_iconTop GitHub Comments

3reactions
ebaauwcommented, Dec 26, 2017

In my experience, you need to npm -g uninstall homebridge explicitly before re-installing it, to force re-compilation of the mdns module. This is needed every time you change NodeJS to a different major version.

1reaction
stale[bot]commented, Sep 6, 2018

This issue has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

NodeJS - Why is node reporting wrong version..?
I have Atom installed, which has it's own version of node installed at: C:\Program Files\Atom\resources\app\apm\bin. The node.exe in here is ...
Read more >
Can I change the version of node.js my project uses?
Yes, you can do so by updating the engines field specified in the package.json project file. Currently, Glitch supports node.js versions 6.17.1 through ......
Read more >
Wrong node version is being used for global install - Reddit
I have installed stable node and the corresponding latest npm version using nvm. The paths for both are as follows:
Read more >
Why I don't have the latest node version? - Ask Ubuntu
I installed node with the command sudo apt install nodejs , and then I check the version with the command node --version and...
Read more >
Jest runs wrong node version with create-react-app - YouTrack
Jest runs wrong node version with create-react-app · Open a CRA project, or create a new one using New Project > React App...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found