Jul 28, 2018 And force the use of stretch repository during install: sudo apt install -t stretch nodejs since install is complete you got all the packages in the expected versions: $ nodejs -v v10.7.0 $ npm. While using the packaged version in the Debian repository is an option for experimentation, installing from a PPA and working with npm or nvm offers additional flexibility. By: Kathleen Juell.
Sign up for GitHub today
GitHub will be home to over 36 million developers working collectively to host and evaluate code, deal with tasks, and develop software collectively.
Sign upPossess a question about this task?Sign up for a free GitHub accounts to open up an concern and get in touch with its maintainers and the area.
By hitting “Signal up for GitHub”, you acknowledge to our terms of assistance and privacy statement. We'll sometimes deliver you accounts related email messages.
Currently on GitHub? Sign in to your account
Comments
mentionedDec 25, 2017
I cannot body out how to install Node.js v9.back button. I ran the subsequent instructions in terminal. But the airport spit out this information: I currently have got v4.8.2 of the nodejs bundle installed on my computer.I furthermore tried operating the adhering to. No dice. Still set up nodejs v4.8.2.If I run update-alternatives -config nodejs , I get 'update-alternatives: error: no options for nodejs' from the port. |
mentionedDec 25, 2017
Run node , notnodejs -nodejs is definitely the name debian provided to the binary for factors they've possibly come to feel dissapointed about over the decades.If you possess the nodejs-legacy bundle installed, uninstall it; it conflicts. No harm in eliminating it, it's just a symlink of/usr/bin/nodejs to/usr/rubbish bin/node . |
commentedJan 3, 2018
I have same problem, any alternative? tip for make use of 'node' doset function. Thanks a lot |
mentionedJan 11, 2018 .edited
edited
Workaround I are using stretch and to get newest node I make use of this npm package deal known as 'n' I first included node 6 to my /etc/appropriate/sources.listing.deb/nodesource.list After that I installed nodejs, after getting nodejs and npm I did, ('#' for basic cover) This will give me most recent node and npm, reinstalling the n package just to feel safer it provides been set up by newer npm. |
commentedFeb 5, 2018 .modified
modified
I acquired the same issue. The debian package deal source concern was increased than the nodesource. I just defined a pin-priority increased and it proved helpful. Confirm the problem:Run: apt-cache policy nodejs For me it has been: There is certainly the problem. The nodesource quantity demands to end up being increased so the deal manager can select it as a supply. The solution:As root: # nano /etc/appropriate/preferences.d/nodejs Set the priority: Examine if it worked well: apt-cache policy nodejs Finaly! Now just attempt the appropriate install once again. |
mentionedFebruary 9, 2018 .modified
modified
apt-cache plan nodejs earnings It seems like they erased the lastest version. Why does Debian feels we're some puppets ? Isn'testosterone levels Linux more than enough idiot-proof to let us dev in an unpredictable environment ?. |
added a commit to Pchelolo/service-runner that referenced this problemFebruary 14, 2018
Don't install npm for build in case nvm will become utilized to install it.
referenced this concernFebruary 14, 2018
MergedDon't install npm for construct in case nvm will become used to install it.#181
added a commit to Pchelolo/service-runner that referenced this issueFebruary 14, 2018
Wear't install npm for construct in case nvm will end up being utilized to install it.
added a commit to wikimedia/service-runner that referenced this issueScar 2, 2018
Put on't install npm for construct in situation nvm will become utilized to install it.
mentionedScar 5, 2018
@jeancarlos'h solution proved helpful perfectly! |
mentionedScar 12, 2018
Also for me. Thank you @jeancarlos |
commentedScar 12, 2018
![Install Install](https://linuxhint.com/wp-content/uploads/2018/05/n-2.png)
closing out as answered, thanks a lot! |
mentionedMar 17, 2018
i nevertheless cannot obtain it function actually i attempted jeancarlos's answer. But rather i use nvm (node version supervisor) and then i can install node 8+ |
left a commentScar 18, 2018
@jeancarlos'h solution proved helpful for me as well. |
left a commentApril 20, 2018
Late to the celebration: A combination of @jeancarlos and @freed00m responses helped me. Initially I was working into the disappointment that no issue what I did apt-cache policy nodejs would often output this:After much annoyance this will be what worked well for me:
Give thanks to you all for your assist! |
commentedMay 8, 2018
Was getting the same concern and anything helps. As this article will be the nearly all relevant, right here's what i did I used the nvm to install npm and node Functions like a attraction right now ;) |
left a commentJun 21, 2018
I obtained same concern setting up node10 with the command word curl -sL https://deb.nodesource.com/setup10.x sudo -At the party - my system configuration is definitely the adhering to rather setting up node8 it worked well like a attraction. thanks, |
commentedMarch 15, 2018 .edited
edited
This is definitely how i was finally able to install nodejs 10 in Debian 9 with these methods: 1- Create nodesource.listing file in /etc/apt/sources.listing.d/ with these lines: deb https://deb.nodesource.com/node10.x stretch out main deb-src https://deb.nodesource.com/node10.x stretch out main 2- sudo apt install curl 3- sudo apt-get upgrade 4- curl -sL https://deb.nodesource.com/set up10.x bash - 5- sudo apt install nodejs 6- sudo apt-get install -y build-essential 7- npm init 8- npm install outlet.io -save And check out the installation with: node -v npm -v |
commentedJanuary 22, 2019
Elizabeth: Ill record in the preferences document /etc/appropriate/preferences.m/nodejs, no Deal header |
mentionedFebruary 7, 2019
Furthermore for me. Give thanks to you @jeancarlos |
left a commentInterest 12, 2019 .modified
modified
Hi, by now, I'meters trying jeancarlos'h method that should become the one but, when I make use of the 10.x and 11.x repos:
Clean (I handicapped the regular debian repo for testing, when I got those, just debian repo apeared after apt-cache policy nodejs) Only with 8.x I obtained a candidate from the repo, anyone knows what'h going on with the repos? Probably has something to do with my machine is usually a 32bit Debian SO and there is no 32bit binary applicant? |
This was referencedJun 5, 2019
Open up
Open
Indication up for freeto sign up for this discussion on GitHub. Currently have got an account? Sign in to remark