-
Notifications
You must be signed in to change notification settings - Fork 255
Node 0.12 vs 0.10 #173
Comments
I think it might make more sense to have a known issues section, rather than saying it works better with 0.10. Since the readme contains ``AirSonos requires node.js >= v0.10.33 installed to run. |
Thanks for posting this! I, too, was having issues with AirSonos on Node 0.12.x, but downgrading to the last 0.10 release (0.10.38) has cleared everything up nicely. (Running on a 10.7.x MacMini OS X that's always on anyways). Totally sad that Sonos won't pay the tax to integrate AirPlay directly, but at least this seems to fit the bill. Will need to get it running automatically as a daemon at boot eventually. |
Can you run AirSonos with a separate install of Node or is a downgrade required? I use Node for other things on my system and don't want to downgrade just for AirSonos. |
@phylaxis, remove the regular node install from your system. Assuming you are using OS X, here are instructions http://stackoverflow.com/questions/11177954/how-do-i-completely-uninstall-node-js-and-reinstall-from-beginning-mac-os-x. Then install NVM, https://github.com/creationix/nvm. Install as many versions of node as you like using NVM. The catch is any global modules you have installed, you will have to reinstall them for every version. But now you can easily switch between versions, install and uninstall. Supports io.js and node. You can also |
I suggest using n (https://github.com/tj/n) instead of nvm, I always had problem with nvm and how it handle the global modules is a bit crazy. |
In case it helps someone else, here are instructions for homebrew and OS X 10.0.5.
Then rebuild airsonos:
|
Now compatible with 0.12 - this should be less of a problem. |
So I've been having a terrible experience with Airsonos until today when I downgraded to NODE 0.10 -> I think somewhere in the documentation it should be mentioned this runs better with 0.10
The text was updated successfully, but these errors were encountered: