Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation recommends using non-supported Node.js #25

Closed
astorije opened this issue Jun 5, 2016 · 1 comment · Fixed by #49
Closed

Documentation recommends using non-supported Node.js #25

astorije opened this issue Jun 5, 2016 · 1 comment · Fixed by #49
Labels

Comments

@astorije
Copy link
Member

astorije commented Jun 5, 2016

The install doc for Ubuntu and Debian says to install Node.js with:

sudo apt-get -y install nodejs-legacy npm

On Debian Jessie, nodejs-legacy is in v0.10. It goes to v4.x in Stretch only, which will not be here before a year.

Same with Ubuntu Trusty Tahr, the current LTS and the following version, Wily Werefolf. It's in v4.x only since the last version, Xenial Xerus, released 2 months ago.

Considering we are dropping support for Node.js v0.10, we should probably specify in the doc that, unless people are running Debian Stretch or Ubuntu Xenial Xerus, they should be installing Node through Nodesource or whatever instead of apt-get. Any suggestions? (Ping @JocelynDelalande, it's been a while 😄).

@JocelynDelalande
Copy link
Contributor

I wanted to opened the very same ticket, so thanks for that :-)

Considering we are dropping support for Node.js v0.10, we should probably specify in the doc that, unless people are running Debian Stretch or Ubuntu Xenial Xerus, they should be installing Node through Nodesource or whatever instead of apt-get. Any suggestions?.

Nodesource Debian repository are the simplest way I know at the moment.

(Ping @JocelynDelalande, it's been a while 😄).

;-) quite busy…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants