Closed thelonious closed 7 years ago
As the readme says, this version does not support the node.js version you use. Upgrade node.js to 4.6 or use the 0.18 version of i2c.
Ah, yes. I didn't read down that far. It's too bad the default experience on Raspian isn't nicer for node. I've switched over to Python for now. Thanks!
Why not upgrading nodejs to 4.6 or above?
Op 8 okt. 2016 16:12 schreef "Kevin Lindsey" notifications@github.com:
Closed #80 https://github.com/kelly/node-i2c/issues/80.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kelly/node-i2c/issues/80#event-817097042, or mute the thread https://github.com/notifications/unsubscribe-auth/AEhQT175mCtBf9gKUIPq-CQCMGsfack0ks5qx6SzgaJpZM4J5lP3 .
I ran out of time with that project and needed a solution right then. I may give node a try next time around. FWIW, I have 'n' running now, so it's easy switch versions. I was able to build i2c with 5.12.0 and 6.6.0 just fine on the Pi 3.
It looks like I'm running node v0.10.29 and npm 1.4.21. When I run
sudo npm install i2c
I get the following:Thanks for any suggestions on how to get around this.