echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc | |
. ~/.bashrc | |
mkdir ~/local | |
mkdir ~/node-latest-install | |
cd ~/node-latest-install | |
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1 | |
./configure --prefix=~/local | |
make install # ok, fine, this step probably takes more than 30 seconds... | |
curl https://www.npmjs.org/install.sh | sh |
# this way is best if you want to stay up to date | |
# or submit patches to node or npm | |
mkdir ~/local | |
echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc | |
. ~/.bashrc | |
# could also fork, and then clone your own fork instead of the official one | |
git clone git://github.com/joyent/node.git | |
cd node | |
./configure --prefix=~/local | |
make install | |
cd .. | |
git clone git://github.com/isaacs/npm.git | |
cd npm | |
make install # or `make link` for bleeding edge |
# take ownership of the folders that npm/node use | |
# please don't do this if you don't know what it does! | |
sudo mkdir -p /usr/local/{share/man,bin,lib/node,include/node} | |
sudo chown -R $USER /usr/local/{share/man,bin,lib/node,include/node} | |
# now just a pretty vanilla node install | |
# let it use the default paths, but don't use sudo, since there's no need | |
mkdir node-install | |
curl http://nodejs.org/dist/node-v0.4.3.tar.gz | tar -xzf - -C node-install | |
cd node-install/* | |
./configure | |
make install | |
# now the npm easy-install | |
curl https://www.npmjs.org/install.sh | sh |
# using Homebrew | |
# Note: `brew install npm` has problems, as of 2010-12-30. | |
# hopefully it will eventually be good and happy. | |
# As of npm@0.2.13, however, this is an option | |
PREFIX=$(brew --prefix) | |
# take ownership | |
# this will also let homebrew work without using sudo | |
# please don't do this if you don't know what it does! | |
sudo mkdir -p $PREFIX/{share/man,bin,lib/node,include/node} | |
sudo chown -R $USER $PREFIX/{share/man,bin,lib/node,include/node} | |
brew install node | |
# now install npm | |
# prefix will default to $(brew --prefix) | |
curl https://www.npmjs.org/install.sh | sh |
echo 'export PATH=$HOME/.local/bin:$PATH' >> ~/.bashrc | |
echo 'export npm_config_userconfig=$HOME/.config/npmrc' >> ~/.bashrc | |
. ~/.bashrc | |
mkdir ~/.local | |
mkdir ~/node-latest-install | |
cd ~/node-latest-install | |
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1 | |
./configure --prefix=~/.local | |
make install | |
curl https://www.npmjs.org/install.sh | sh |
# install node wherever. | |
# use sudo even, it doesn't matter | |
# we're telling npm to install in a different place. | |
echo prefix = ~/local >> ~/.npmrc | |
curl https://www.npmjs.org/install.sh | sh |
This comment has been minimized.
This comment has been minimized.
For me the 2nd one worked ^^ thx |
This comment has been minimized.
This comment has been minimized.
First one worked perfectly, although on a Debian x64 512M RAM it did not perform in 30 seconds.
HAH! NEVERMIND! Didn't work, Edit: I retried after I cleaned up some node-related directories, binaries and installs. I uninstalled The self-compiled |
This comment has been minimized.
This comment has been minimized.
First option worked well for me once I realize that the path of node is important. I.E. I had node previously installed to usr/local not my ~/local. I pushed my ~/local to have higher precedence in the path and the npm installation worked without a hitch. Addendum: As I had 'system' node and a local node installed, when I borked up my paths and the system node was running, all my paths were screwed when doing requires in my code, forcing the local 'node' to be my executable fixed all my path issues. Ex: 'which node' returns a path to my ~/jbateman/local installation instead of /usr/local/bin |
This comment has been minimized.
This comment has been minimized.
seems like someone is keeping ports up to date as well... |
This comment has been minimized.
This comment has been minimized.
For the take-ownership script, you first need to create /usr/local/lib/node and /usr/local/include/node.
|
This comment has been minimized.
This comment has been minimized.
Thanks, Robert, good catch. Fixed. |
This comment has been minimized.
This comment has been minimized.
The 2nd script (only-git-all-the-way.sh) has a wrong URL for cloning node. It should read: git clone https://github.com/ry/node.git instead of git clone git://github.com/ry/node.git |
This comment has been minimized.
This comment has been minimized.
ok..cool. |
This comment has been minimized.
This comment has been minimized.
If your on a MAC remember your ".bashrc" isn't used, it should be ".bash_profile" |
This comment has been minimized.
This comment has been minimized.
Thanks for share!! good work! |
This comment has been minimized.
This comment has been minimized.
For the only-git-all-the-way script, the location of node.git should be updated: |
This comment has been minimized.
This comment has been minimized.
@rbotman: Thanks. |
This comment has been minimized.
This comment has been minimized.
There's a reference to |
This comment has been minimized.
This comment has been minimized.
There is one quite nasty error in only-git-all-the-way.sh example: There should be |
This comment has been minimized.
This comment has been minimized.
Re: https://gist.github.com/579814#file_take_ownership.sh Just a note: make install does not work without sudo. |
This comment has been minimized.
This comment has been minimized.
Help !! Also if I try the git all the way i get this |
This comment has been minimized.
This comment has been minimized.
I have observed this as well. Cygwin is really terrible in how it
handles child processes. There is basically no way around this.
You can try `curl http://npmjs.org/install.sh | npm_install=rc sh` to
install the 1.0 release candidate, which handles Cygwin a little
better. But, really, the best answer is to either wait for a native
windows port of node, or use use something like VMWare or VirtualBox
to run an Ubuntu virtual machine.
|
This comment has been minimized.
This comment has been minimized.
May i know how to upgrade node.js? just run the same command again? |
This comment has been minimized.
This comment has been minimized.
Hey devlim, try running one of these again, it should work (if you can remember, try to use the same one as last time, but either way it should work fine). |
This comment has been minimized.
This comment has been minimized.
Thank DTrejo. |
This comment has been minimized.
This comment has been minimized.
What is the rationale for installing to ~/local in so many of these? |
This comment has been minimized.
This comment has been minimized.
I think it is to separate node and the node related tools from the rest of the system. This is preferrable since NodeJS is in rapid development and is rarely or never available from the package manager in it's latest version. Since it is separated from the global program installation folders, it's not as easily lost and forgotten, not so much for disk space, perhaps, but more for the principle. |
This comment has been minimized.
This comment has been minimized.
Some more info here:
http://blog.nodejs.org/2011/04/04/development-environment/
|
This comment has been minimized.
This comment has been minimized.
@brandondrew The point is that software you install and develop
should go somewhere you own and manage.
I install node and npm into /usr/local on my mac. I also have
chown'ed that directory to my user account. On servers and other
"production" machines that I'm not as intimate with, I install
everything into ~/local.
There are two points at work here:
1. Don't do things you don't understand, or clobber things that aren't yours.
2. Try very hard not to destroy your ability to revert to a "clean" environment.
If you install into /usr/local, you can always revert to the initial
state by removing that directory (and with it, all the user-installed
software). The system stuff will be in the base of /usr (or even the
top-level /lib, /var, etc.)
If you install into your home directory, you have only to log in as a
different user to see a pristine environment.
I recommend installing into your home directory if you aren't 100%
clear about what's going on in /usr/local, and comfortable manually
managing it.
…On Mon, Apr 25, 2011 at 17:28, brandondrew ***@***.*** wrote:
It says "Software that you compile yourself should _not_ go into /usr, it should go into your home directory. This is part of being a software developer."
That's an assertion without any explanatory rationale. Dan Benjamin made a similar assertion a few years ago, but he asserted (if I recall correctly) that you should put everything in /usr/local/bin/.
Such assertions will kowtow some people into complying, but that's a shame. I think it's much better to ask for, and give, reasons.
Please understand that I'm not necessarily disagreeing: I'm just saying "why _there_!?". I tend to agree that the home directory is better than /usr/local/bin, but /usr/local/bin was _supposedly_ a convention for user-compiled stuff. ~/local seems to be a brand-new convention, that I've only seen with Node.js.
##
Reply to this email directly or view it on GitHub:
https://gist.github.com/579814
|
This comment has been minimized.
This comment has been minimized.
I'm getting the same error as edlongman trying to run |
This comment has been minimized.
This comment has been minimized.
Hey guys make sure that the last line of code in your bashrc file is not a comment as the appending will lead you to a commented out PATH=$HOME/local/bin:$PATH which means the install will fail. |
This comment has been minimized.
This comment has been minimized.
I updated the code at a fork of the gist here: https://gist.github.com/957346 If there is a way of doing a pull request for a gist I can't seem to find it. |
This comment has been minimized.
This comment has been minimized.
When I did the install as superuser (take-ownership) route I got an error: anyone have any ideas? |
This comment has been minimized.
This comment has been minimized.
In referance to the second method "only_git_all_the_way.sh". I ran into a problem with installing npm. The way that I resolved the issue was to once my .bashrc file was updated (line 5), I added |
This comment has been minimized.
This comment has been minimized.
@jtmkrueger: the pkgconfig command is used by various build utilities to determine what you have installed on a system without needing to dig through output from various platform-specific package managers (e.g. build sequence needs to know where you have installed lua, so it looks for /usr/lib/pkgconfig/lua.pc, /usr/local/lib/pkgconfig/lua.pc, etc until it finds one and in that file there is a listing of where the various lib and bin dirs are for that package.) If this is the first major package you have installed in /usr/local then it is possible that the pkgconfig directory does not exist. Try running (as root/sudo) "mkdir /usr/local/lib/pkgconfig" and then install again. |
This comment has been minimized.
This comment has been minimized.
Please fix only-git-all-the-way.sh as per the above comment. |
This comment has been minimized.
This comment has been minimized.
First one worked! Woot! This should be the default. I had problems with it the first two times I tried. |
This comment has been minimized.
This comment has been minimized.
Hi i've got such problem with npm on ubuntu 11.04: mkdir ~/local
echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
# could also fork, and then clone your own fork instead of the official one
git clone git://github.com/joyent/node.git
cd node
./configure --prefix=~/local --without-ssl
make install
cd ..
git clone git://github.com/isaacs/npm.git
cd npm
make install Maybe anyone could help me: what if i want to install node.js to /media/lazersluts/nodejs, what should i do. Update Solved with echo prefix = ~/local >> ~/.npmrc
curl http://npmjs.org/install.sh | sh |
This comment has been minimized.
This comment has been minimized.
Why does require('npm-name'); work only on partition where node.js installed? And doesn't on other partitions? |
This comment has been minimized.
This comment has been minimized.
I had to do sudo make install in the first solution. Also I had problems with npm: http://stackoverflow.com/questions/6383413/npm-install-issues-ubuntu-11-04 |
This comment has been minimized.
This comment has been minimized.
In Ubuntu, you may need to do |
This comment has been minimized.
This comment has been minimized.
'install' finished successfully (12m33.358s) |
This comment has been minimized.
This comment has been minimized.
None of these worked for me as node gave me an out of memory error trying to run the node cli.js command. I was eventually able to get it working by loading the .pkg file here https://sites.google.com/site/nodejsmacosx/ |
This comment has been minimized.
This comment has been minimized.
@triptych Were you using node master? If so, update today and
rebuild. Note that the git master is usually pretty unstable, so if
there's ever any problem, you should try with a released version, or
by checking out a release tag or the v0.4 branch, and building that.
…On Mon, Sep 5, 2011 at 01:15, triptych ***@***.*** wrote:
None of these worked for me as node gave me an out of memory error trying to run the node cli.js command. I was eventually able to get it working by loading the .pkg file here https://sites.google.com/site/nodejsmacosx/
##
Reply to this email directly or view it on GitHub:
https://gist.github.com/579814
|
This comment has been minimized.
This comment has been minimized.
Thankyou, my node/npm install got corrupted "somehow" , the first method about worked for me |
This comment has been minimized.
This comment has been minimized.
I tried the first one using cygwin and I'm stuck with this: curl http://npmjs.org/install.sh | sh Written by John Gilmore and Jay Fenlason. If I try the second, and run make install it seems to run forever at buid-doc.sh. |
This comment has been minimized.
This comment has been minimized.
I had to add:
before line 10 in order for https://gist.github.com/579814#file_use_nave.sh to work properly. Did I miss something? |
This comment has been minimized.
This comment has been minimized.
I am trying to install this using homebrew and I seeing the following permissions error.
It looks like the install for npm is failing: To get this working I added
I probably could also have run it the install command with sudo like this:
but the point of this gist is to install node and npm without having to sudo. However, at the end of the title at the top of this gist it says that npm >=0.3 is safer when using sudo. I am not sure if that means that you should install using sudo or chown the directory to $USER |
This comment has been minimized.
This comment has been minimized.
http://nodejs.org/dist/node-latest.tar.gz - 404 not found |
This comment has been minimized.
This comment has been minimized.
which node.js version is the latest who support i386 MacOSX 10.5.8 ? |
This comment has been minimized.
This comment has been minimized.
Good to know: http://nodejs.org/dist/node-latest.tar.gz links to v0.6.4 but the latest is v0.6.5 (http://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz). |
This comment has been minimized.
This comment has been minimized.
top one worked great for me on Ubuntu Server 11.04. thanks! |
This comment has been minimized.
This comment has been minimized.
how do i update node.js? i tried the first 2 methods and got the same error src/unix/ev/ev.c: In function ‘ev_io_start’: |
This comment has been minimized.
This comment has been minimized.
In https://gist.github.com/579814#file_only_git_all_the_way.sh, there is no need to git clone the npm repo, as it is now made available when you install node itself. So can remove line numbers 15-18. Also, this is how the node installation ended for me: shebang #!~/local/bin/node Though everything seems to be working ("node -v", "npm -v" returns proper values, and "npm install -g coffee-script" works), not sure why the above error happened, and what the implications are. Jotting it down here since someone else too might face the issue. |
This comment has been minimized.
This comment has been minimized.
Just a note, you can't use the ~ for the reference to home and currently npm doesn't work with 0.9.0-pre so the git method fails |
This comment has been minimized.
This comment has been minimized.
Running Ubuntu 12.04, I kept running into this error when running
My vm was brand spanking new, so I had to install this before
|
This comment has been minimized.
This comment has been minimized.
Just used the first one at Amazon EC2, awesome, thanks. |
This comment has been minimized.
This comment has been minimized.
I don't know why installing npmjs didn't work using the first method but this is what I'm getting. npm ERR! System Linux 3.5.0-27-generic
make: Nothing to be done for `doc'. npm ERR! System Linux 3.5.0-27-generic |
This comment has been minimized.
This comment has been minimized.
apparently you still need admin rights to install npm. I just had the same issue, so I manually downloaded the install script and "sudoed" it: cd ~ No error messages so apparently it worked :) |
This comment has been minimized.
This comment has been minimized.
This helped me out... and in my case, (CentOS 6.3) EPEL repo has this jewel of a software, so it is a reliable package maintainer... This was really easy. https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager |
This comment has been minimized.
This comment has been minimized.
I am getting this error in both method 1 and 2. Can someone please help? root@web [/node]# ./configure --prefix=~/local |
This comment has been minimized.
This comment has been minimized.
I got an error at the same step as above except a different line: bash-3.2$ ./configure --prefix=~/local |
This comment has been minimized.
This comment has been minimized.
Nevermind, looks like I was using an old Python version: |
This comment has been minimized.
This comment has been minimized.
Worked here. Ubuntu 13.04 64 bits. Thanks :) |
This comment has been minimized.
This comment has been minimized.
First one is not working for me also. Someone pls help. [root@sddev node-latest-install]# ./configure --prefix=~/local |
This comment has been minimized.
This comment has been minimized.
top worked beautifully! thanks man! |
This comment has been minimized.
This comment has been minimized.
Step 9, method 1: "npm cannot be installed without nodejs. "Maybe node is installed, but not in the PATH? |
This comment has been minimized.
This comment has been minimized.
The configure script for only-git-all-the-way.sh is in python2 - this will cause parse errors if python3 is the default on your system. One solution is to add a symbolic link to python2 inside your ~/local/bin. cd ~/local/bin |
This comment has been minimized.
This comment has been minimized.
I thought "PROFESSIONALS" developed node.js????? It is a garbage install process for the mac. The install directory is hidden/protected: /usr/local/bin... WTF? |
This comment has been minimized.
This comment has been minimized.
It is hard to have ANY confidence in developers that can NOT even get an installer right. |
This comment has been minimized.
This comment has been minimized.
Can you imagine if surgeons and real professionals did their work so poorly? I am obviously very pissed that I just wasted two hours on what should be simple. |
This comment has been minimized.
This comment has been minimized.
@itcastro maybe you should do something else if you failed to open http://nodejs.org/ and download installer in the first place. |
This comment has been minimized.
This comment has been minimized.
./configure --prefix= ./configure --prefix=$HOME/local |
This comment has been minimized.
This comment has been minimized.
I love this.....works like charm Thank you so much! |
This comment has been minimized.
This comment has been minimized.
Thanks!! No 30 seconds here.... |
This comment has been minimized.
This comment has been minimized.
Hi all - I'm pretty new to this but I read (and confirmed that it works for me) that using make -j (so with the -j flag) uses all processor cores and in my case (8 cores) makes it go A LOT faster. |
This comment has been minimized.
This comment has been minimized.
On "take-ownership", the directory structure for the node dist is wrong. curl http://nodejs.org/dist/node-v0.4.3.tar.gz | tar -xzf - -C node-install should be curl http://nodejs.org/dist/v0.10.20/node-v0.10.20.tar.gz | tar -xzf - -C node-install |
This comment has been minimized.
This comment has been minimized.
node-and-npm-in-30-seconds.sh ftw \m/ thank you so much! |
This comment has been minimized.
This comment has been minimized.
@leto, ./configure --prefix=$home/local fixed the issues I was having with #2. Thanks! |
This comment has been minimized.
This comment has been minimized.
The first one doesn't work on OSX 10.9. |
This comment has been minimized.
This comment has been minimized.
Actually, the problems with #2 are fixed with |
This comment has been minimized.
This comment has been minimized.
Thank you very much..I have installed node in ubuntu. |
This comment has been minimized.
This comment has been minimized.
I'm also getting this with the 30 second method. "npm cannot be installed without nodejs. Maybe node is installed, but not in the PATH? I'm pretty sure node installed although i do not seem to be able to run it. do i just delete /node-latest-install if i would want to try another method? |
This comment has been minimized.
This comment has been minimized.
@johan010 npm comes packaged with nodejs now so you can ignore the part about installing npm |
This comment has been minimized.
This comment has been minimized.
i used nvm which gives you the added bonus of easy node.js-version switching: # see more about nvm: https://github.com/creationix/nvm # added bonus: gives you the opportunity to switch node versions # install nvm curl https://raw.github.com/creationix/nvm/master/install.sh | sh # reload bash_profile source ~/.bash_profile # install a node.js version, edit the version you want to use nvm install v0.10.22 |
This comment has been minimized.
This comment has been minimized.
Wow - wish i'd found this page like a year ago. :) stackoverflow answer is crap. |
This comment has been minimized.
This comment has been minimized.
Wonderful... |
This comment has been minimized.
This comment has been minimized.
This is beautiful. |
This comment has been minimized.
This comment has been minimized.
In addition to the first script, I run this on new systems for easy sudo'ing, when (rarely) needed:
|
This comment has been minimized.
This comment has been minimized.
Just as a heads up, for the "node-and-npm-in-30-seconds.sh" gist I had to add www to the npmjs URL since it was returning HTML. Ex: $ curl --proxy [proxy here] https://npmjs.org/install.sh install.sh |
This comment has been minimized.
This comment has been minimized.
Hi Isaac, I have updated the 30 seconds install to the new npm url. Here is the link to the gist https://gist.github.com/aebm/9047011 Regards |
This comment has been minimized.
This comment has been minimized.
Can someone explain what each step in "node-and-npm-in-30-seconds.sh" does? I'd like to know the reasons behind each line. |
This comment has been minimized.
This comment has been minimized.
Hi Isaac I am trying to use the npm install procedure "node-and-npm-in-30-seconds.sh" (actually part of a Dockerfile I am creating to install cartoDB). The final output is this: ... Do you have any idea what can cause this? |
This comment has been minimized.
This comment has been minimized.
Hi Isaac When I try the second script (again, inside Docker), it also fails with this message: Cloning into 'npm'... |
This comment has been minimized.
This comment has been minimized.
hi Isaac/guys couldn't execute the 30-secs-way without errors. Even I tried to fix it with no luck by playing around with most of the aforementioned variants. So just went to nodejs.org and click install. It downloads the latest node dist. Then, I followed the readme instructions and got node installed (it seems that it comes with npm now) My question is, am I missing something installing node+npm in this way? Thanks, |
This comment has been minimized.
This comment has been minimized.
Just a note, right now npmjs.org is throwing 301 redirects when you try and access without prefixing the www subdomain https://npmjs.org/install.sh e.g. curl -v https://npmjs.org/install.sh The solution is to either manually change for the redirect curl -v https://www.npmjs.org/install.sh Or just use the -L option to tell curl to follow redirects curl -Lv https://www.npmjs.org/install.sh After making one of those changes, the gists should work. |
This comment has been minimized.
This comment has been minimized.
Just updated the scripts to add the www to the urls. Sorry about that, folks. |
This comment has been minimized.
This comment has been minimized.
For some reason after maybe a restart yo command not found and also the same for npm. This was bugging me as it was happening after time periods...thought it must be a restart... and running . ~/.bashrc solved my issue ! So how do I persist this ? In this file I have export PATH=$HOME/local/bin:$PATH I thought those 2 lines would export the lines in the main paths file ? So I guess I might need these added to my main etc/paths file right (but why didnt the exports work???) [paths file] can I add it like ~/local/lib ?? |
This comment has been minimized.
This comment has been minimized.
The link http://joyeur.com/2010/12/10/installing-node-and-npm/ is not active now. |
This comment has been minimized.
This comment has been minimized.
That link is now https://www.joyent.com/blog/installing-node-and-npm |
This comment has been minimized.
This comment has been minimized.
ict4eo, I was getting the same error on my ubuntu system for the 2nd script and realized that it was compiling into the wrong directory (it actually made a directory named "~" in the current directory rather than using the home directory). I changed: But I would grateful if someone could explain why the tilde did not work. |
This comment has been minimized.
This comment has been minimized.
The homebrew install should be |
This comment has been minimized.
This comment has been minimized.
@sungwon same thing here. running that second script threw me into a world of pain. took me 1 hour to figure out what the problem was. |
This comment has been minimized.
This comment has been minimized.
First method worked, even thought it took a lot more than 30 seconds. Thanks. |
This comment has been minimized.
This comment has been minimized.
First method helped me move forward with node. Thanks! One note: npm is included with the node install, so I skipped the last step and works fine (use "npm -v" to see which version you have). |
This comment has been minimized.
This comment has been minimized.
I installed nave like
Permission denied? Huh. It has all the correct permissions in /usr/local/bin:
but I can run nave with I'm using Ubuntu 14.04 and ZSH here. Any clues? |
This comment has been minimized.
This comment has been minimized.
Couldn't install properly with BREW for some reason. Used the top .sh and it was flawless. Thanks for the scripts! |
This comment has been minimized.
This comment has been minimized.
Note for anyone having trouble with installing/using node and or npm (especially after restarting the terminal) - For me the |
This comment has been minimized.
This comment has been minimized.
I use the second, and it works. |
This comment has been minimized.
This comment has been minimized.
the last one ... piping curl into your shell ... this is clearly a joke isnt it? |
This comment has been minimized.
This comment has been minimized.
30-second one worked for me. Can't believe this post is over 4-years old and still timely. |
This comment has been minimized.
This comment has been minimized.
Regarding
Thanks! |
This comment has been minimized.
This comment has been minimized.
@mkalygin you should never use sudo for npm installation. http://stackoverflow.com/questions/18212175/npm-yo-keeps-asking-for-sudo-permission/18277225#18277225 |
This comment has been minimized.
This comment has been minimized.
On my gentoo system I get: export PYTHON=/usr/bin/python2.7 ../../src/weak_collection.js ../../src/promise.js ../../src/object-observe.js ../../src/macros.py It seems like something does not honor the $PYTHON setting and is just calling "python" which gives python3 and the above error |
This comment has been minimized.
This comment has been minimized.
I thought the first one might work, but it didn't. But I also forgot to install build-essentials. Either way, I went with the way I usually use, which is: mkdir ~/local
tar -zxvf node* |
This comment has been minimized.
This comment has been minimized.
For the record, I was having problems with the npm easy-install process. Just changed it to exec the script with sudo after its download and got it to work:
|
This comment has been minimized.
This comment has been minimized.
First one gave me these errors: npm ERR! Error: EACCES, mkdir '/usr/local/share/man/man1' npm ERR! System Linux 3.13.0-24-generic |
This comment has been minimized.
This comment has been minimized.
Git, path problem.
Following the instructions it's actually installed to |
This comment has been minimized.
This comment has been minimized.
I would add a note about python version early on. It it would be accepted, I would write a PR to add portability. At the very least, make some noise about using py2 and crashing-out explicitly |
This comment has been minimized.
This comment has been minimized.
Thanks Isaac! This is the gift that keeps on giving (for four years now, apparently). I just ran the top scripts on Ubuntu (Lubuntu) 14.04 Trusty and it ran perfectly and quickly, I just had to install Curl before step #6. |
This comment has been minimized.
This comment has been minimized.
Neatest method I've found:
|
This comment has been minimized.
This comment has been minimized.
Hey man, thanks!! The first one worked for me! |
This comment has been minimized.
This comment has been minimized.
re: node-and-npm-in-30-seconds.sh
resulted in
seems that npm is part of node so is there still need for it? as even without it I got: which npm
~/local/bin/npm |
This comment has been minimized.
This comment has been minimized.
Tried the first method and it failed reporting syntax errors in ./configure |
This comment has been minimized.
This comment has been minimized.
The link |
This comment has been minimized.
This comment has been minimized.
@harleyhar you are probably using wrong python to install. instead of py3k try:
for me, that fixed the issue you seemed to be having |
This comment has been minimized.
This comment has been minimized.
I installed node-and-npm-in-30-seconds.sh with success: BENs-MacBook-Air:~ benodonohue$ ls I get this when i run npm -v: Is someone able to tell me what i may have done or doing wrong? UPDATE: Thanks.. |
This comment has been minimized.
This comment has been minimized.
I made a slight revision to this here for homebrew:
|
This comment has been minimized.
This comment has been minimized.
WONDERFULL!!! |
This comment has been minimized.
This comment has been minimized.
Hello, I tried to install Semantic UI using the git only method. I went through the installation and after "npm install" ( http://learnsemantic.com/guide/expert.html#project-dependencies ) I got an error about gulp version. Then I tried to update gulp with npm and got an error message saying that node version is not correct (sorry I lost the messages and I don't remember version numbers). |
This comment has been minimized.
This comment has been minimized.
I tried the second one, and it ended up creating a literal " Changing to --prefix=/home/username/local seems to fix it. But that's weird... |
This comment has been minimized.
This comment has been minimized.
I received an error today installing 'node-and-npm-in-30-seconds.sh' in my Vagrant provision with the npm part which was not happening last week. Using 'curl -L https://npmjs.org/install.sh | sh' instead (as suggested on npmjs.com) resolved my problem. Cheers~ |
This comment has been minimized.
This comment has been minimized.
tl;dr - any reason not to just grab the binary? |
This comment has been minimized.
This comment has been minimized.
I had the same problem and solution as cristovaov |
This comment has been minimized.
This comment has been minimized.
Had the same problem as cristovaov - curl -L https://www.npmjs.org/install.sh | sh (added -L to follow redirect) worked. |
This comment has been minimized.
This comment has been minimized.
@isaacs, all of the scripts should have |
This comment has been minimized.
This comment has been minimized.
Thanks,
|
This comment has been minimized.
This comment has been minimized.
Thanks for the gists, I've used the 'node-and-npm-in-30-seconds.sh' plenty of times with success. I do agree with easingthemes and Aedx that @isaacs should update the code with the up-to-date curl. For what it's worth, if you are on a completely fresh install of ElementaryOS you might need to install g++ make first. I could get any of @isaacs scripts to work when I first tried (a while back) and had to do:
After that, the 30 second method worked smoothly (when remembering |
This comment has been minimized.
This comment has been minimized.
Thanks, this is great. Great success with 'node-and-npm-in-30-seconds.sh'. FWIW, |
This comment has been minimized.
This comment has been minimized.
using these methods, how does one then update node? i tried to install n using npm and it didn't seem to work. when i issued the command |
This comment has been minimized.
This comment has been minimized.
Thanks. I ran into some problems using sudo to install node and find here some good options to do it without sudo nor need to change /usr/local permissions. But, I was wondering why the command "curl https://www.npmjs.org/install.sh | sh" is needed. I chose the "xgd-freedesktop.org-style.sh" option and put line by line in terminal. But, after the "make install" command I tested if node was ok and it worked like a charm, then, by curiosity, I tested if npm was already installed together, because npm now come with node installer, and yes, npm was installed and fully functional. So, the question is: Why run the "curl https://www.npmjs.org/install.sh | sh" command is required? p.s.: Sorry about my english, I am a huehuebr... |
This comment has been minimized.
This comment has been minimized.
This should be changed: https://www.npmjs.org/install.sh
|
This comment has been minimized.
This comment has been minimized.
I used I replaced this with an explicit path and it seemed to work. Specifically, I did this: git clone git://github.com/joyent/node.git
cd node
./configure --prefix=/home/myusername/local
make install |
This comment has been minimized.
This comment has been minimized.
Much to my great frustration, nowhere, could I really find a complete and concise method of installing the full node stack that did not involve using sudo or some drawn out tedious, solution (and neither the official node site or stackexchange helped here).... As well, all of the sites I visited said that npm was included with the nodejs module yet the nodejs version existing in the default Ubuntu repository did not seem to have it. To save others similar frustrations, I thought I would sketch out the steps I took to install the nodejs stack onto Ubuntu 12.04, "Precise" (elementary): Also, since nvm uses the name "node" instead of "nodejs", make sure that the unrelated program also named "node" -- the Amateur Packet Radio -- does not already exist on your system. sudo apt-get install git build-essential libssl-dev curl git-core wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.23.3/install.sh | bash (I determined the latest nvm version available -- and a lot of other, really helpful information -- at: https://github.com/creationix/nvm) To have nvm automatically sourced, accessible at login: vi ~/.bashrc Now, as root (of course): nvm install stable To set a default version to be used in any new shell, use the alias 'default': Notice that nvm installs everything to the ~/.nvm directory (circumventing the usual requirement and inherent danger of requiring sudo to be used for installing nodejs and its scripts): And if you want Ionic to be installed as well, as I did: |
This comment has been minimized.
This comment has been minimized.
Debian Sid user here, used the first script with two changes
To
as well as added -L to
|
This comment has been minimized.
This comment has been minimized.
@deesejohn Thank you very much! |
This comment has been minimized.
This comment has been minimized.
Hi npm install gave me these errors: npm ERR! install Couldn't read dependencies npm ERR! System Linux 3.2.0-68-virtual |
This comment has been minimized.
This comment has been minimized.
Linux Mint 17 here. The first method almost worked as-is for me except the path added to .bashrc in line#1 wasn't quite right so when attempting to start node at the CLI I was getting the following message echoed back:
So in my home directory I edited .bashrc:
..and changed the line that contained: After that I was able to |
This comment has been minimized.
This comment has been minimized.
Top one worked wonders for me. |
This comment has been minimized.
This comment has been minimized.
Simplest way:
|
This comment has been minimized.
This comment has been minimized.
Thank you for this, the top one worked for me! |
This comment has been minimized.
This comment has been minimized.
oh, by the way, for #1, the curl url is wrong, instead use: curl https://raw.githubusercontent.com/creationix/nvm/v0.24.0/install.sh | bash |
This comment has been minimized.
This comment has been minimized.
Should be changed to
|
This comment has been minimized.
This comment has been minimized.
forgive my ignorance, but i don't understand how to use this, can help ?(: my OS is Fedora 21(: |
This comment has been minimized.
This comment has been minimized.
Having spent 2 hours trying to get node/npm working properly in elm OS, I found this, used the top one.. everything working perfectly now. Thank you very very much! |
This comment has been minimized.
This comment has been minimized.
Having trouble getting the first option to work. Maybe it would help if there were some explanation about what these commands do? what does the second line My guess is that these are trying to install into ~/local and that's why you place that in the path. If so, that did not work for me. I had to put |
This comment has been minimized.
This comment has been minimized.
As Jakobud says, the install url for npm has moved permanently from npmjs.org to npmjs.com |
This comment has been minimized.
This comment has been minimized.
I tried the first method and kept getting stuck. Then yesterday I tried the second method (git-all-the-way) and it managed to work with a few modifications. Made a gist if anybody else wants to see: https://gist.github.com/monsteronfire/adcfd633aa78cfb72c60#file-node-npm-no-sudo |
This comment has been minimized.
This comment has been minimized.
The first version did not work until I read post by gitjeff05 and added: As for the npm, this worked: |
This comment has been minimized.
This comment has been minimized.
Just needed to compile node, so the first option worked easy enough. Thank you! |
This comment has been minimized.
This comment has been minimized.
link at the top is dead: http://joyeur.com/2010/12/10/installing-node-and-npm/ |
This comment has been minimized.
This comment has been minimized.
@leto Using ./configure --prefix=$HOME/local per your suggestion helped OOTB Ubuntu 14.04 with method #1. |
This comment has been minimized.
This comment has been minimized.
@isaacs , i could not get very first solution node-and-npm-in-30-seconds.sh work. And it ran over a minute and did bunch of stuff. Can you tell me how to clean and undo whatever this would have done? |
This comment has been minimized.
This comment has been minimized.
I would suggest to have -j 8 as a command line argument for all make instantiations in all scripts. It does not hurt as far as I know. |
This comment has been minimized.
This comment has been minimized.
On the "30 second" version (1st) I get: xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance Installing Xcode shouldn't be a prerequisite to the "quick'n'dirty" solution IMHO |
This comment has been minimized.
This comment has been minimized.
Long time ago I used "30 sec" version and it served me fine.
Thanks again. |
This comment has been minimized.
This comment has been minimized.
if you installed node with nvm, this also works:
|
This comment has been minimized.
This comment has been minimized.
I installed using git all the way and this works (so far) but only in one terminal window, if I open a second window i get the classic |
This comment has been minimized.
This comment has been minimized.
Yet the first script does not work on all distribs. |
This comment has been minimized.
This comment has been minimized.
I use the first and worked for me! Thanks a lot.. |
This comment has been minimized.
This comment has been minimized.
@cazzoo Thank you. I'm running Debian 7 and the PATH setup didn't work (i couldn't just execute #node anywhere) but with your tip it works. |
This comment has been minimized.
This comment has been minimized.
i'm trying the first script but after executing (with no errors) the node-latest-install exists but the node command does nothing. i cant see any executable anywhere in the folder tree. do i need to add something to /bin somewhere. thanks. |
This comment has been minimized.
This comment has been minimized.
mysolbb I had the same error the thing is you have to install as root first step :sudo su |
This comment has been minimized.
This comment has been minimized.
I tried the first script. The last one didn't work. It showed curl https://www.npmjs.org/install.sh | sh So I tried following (I got from here http://stackoverflow.com/a/15508817/2353403 ) But it's showing the error. node is not found npm cannot be installed without node.js. Maybe node is installed, but not in the PATH? PATH=/home/myuser/local/bin:/usr/lib/jvm/java-7-oracle/bin:/usr/lib/jvm/java-7-oracle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games |
This comment has been minimized.
This comment has been minimized.
|
This comment has been minimized.
This comment has been minimized.
For the top script, I had to change the following:
to
and
to
Everything else worked fine. Ubuntu Server 14.04.2 LTS |
This comment has been minimized.
This comment has been minimized.
In the script we need to change https://www.npmjs.org/install.sh to https://www.npmjs.com/install.sh. |
This comment has been minimized.
This comment has been minimized.
For script node-and-npm-in-30-seconds.sh, I found the same issue as c9jsester. The original configure prefix argument just shoved everything in a sub folder named ~ in the ~/node-latest-install directory. Not sure why that failed. I actually split the curl command and install command:
Running on Linux Mint 17. |
This comment has been minimized.
This comment has been minimized.
Same problem as c9jsester and wltiii. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The third option is an aberration on Linux and a security breach. |
This comment has been minimized.
Used the top one, and it worked great. Thanks :)