6 ms·

Node.js 0.4.5 Released w/ many bug fixes

43 points by chapel 16y ago

bauchidgw 16y ago
awesome, but could somebody explain a unix noob on whats the easiest way to update an existing node.js (ubuntu) installation?
- olalonde 16y ago
  Just install the new version, it will overwrite the previously installed version.
- bootload 16y ago
  "... the easiest way to update an existing node.js (ubuntu) installation? ..." The latest vid from ryan ~ http://blog.nodejs.org/2011/03/17/welcome-to-the-node-blog/ http://blog.nodejs.org/2011/03/17/welcome-to-the-node-blog/ explained the need to download & install from source. This presumes you have V8 installed. Holler if you get into trouble I've installed a few times on Ubuntu 8.04 Hardy Heron.
  - kragen 16y ago
    You mean, he explained that it was necessary to build from source, and why? Is this information available in textual form?
    - bootload 16y ago
      "... You mean, he explained that it was necessary to build from source, and why? Is this information available in textual form? ..." It isn't 100% necessary. You can install from binaries. But as node is a moving target as a dev you get the best feature set/bug fixed version, faster. The talk hasn't been transcribed to my knowledge. Why not view the vid or ask @ryan or irc://irc.freenode.net#freenode why from source? The install instructions here ~ https://github.com/joyent/node/wiki/Installation https://github.com/joyent/node/wiki/Installation or install binaries here ~ https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager https://github.com/joyent/node/wiki/Installing-Node.js-via-p...
  - rmg42 16y ago
    Isn't the v8 source included in node and built as part of the build process? deps/v8?
    - bootload 16y ago
      "... Isn't the v8 source included in node: V8 is included in the Node distribution. To use TLS, ..." Yes, right. From v1 (I only looked back to 1) V8 is installed. I install it anyway.
- deleted 16y ago
  [deleted]
- dualogy 16y ago
  I have written the following script for this. Update all the version numbers for the next update. Somehow I was too lazy to make this a variable. Downloads the Node TAR.GZ to the current folder and extracts, so put this in some extra folder such as "node_setup". And run the script with sudo. #!/bin/bash apt-get install build-essential g++ curl libssl-dev apache2-utils pkg-config wget http://nodejs.org/dist/node-v0.4.5.tar.gz gunzip node-v0.4.5.tar.gz tar -xf node-v0.4.5.tar cd node-v0.4.5 ./configure make make install
  - fullmoon 16y ago
    Just wanted to share a little trick that I like very much curl http://nodejs.org/dist/node-v0.4.5.tar.gz http://nodejs.org/dist/node-v0.4.5.tar.gz | tar -zxvf - -z GZip compressed input -x Extract -v Verbose -f File
- selectnull 16y ago
  I use ppa: sudo add-apt-repository ppa:jerome-etienne/neoip sudo apt-get update sudo apt-get install nodejs I got 0.4.5 this morning from the usual upgrade, before I even saw the news.
  - dualogy 16y ago
    Awesome, I like your approach even better than mine (below). Switched to this but will keep my script for my future users in case they're NodeJS noobs...
  - ashchristopher 16y ago
    On 64-bit Ubuntu you will only get 0.2.6 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: nodejs 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 0B/1,834kB of archives. After this operation, 5,349kB of additional disk space will be used. Selecting previously deselected package nodejs. (Reading database ... 57171 files and directories currently installed.) Unpacking nodejs (from .../nodejs_0.2.6~lucid1~ppa201101061407_amd64.deb) ... Setting up nodejs (0.2.6~lucid1~ppa201101061407) ...
- rjrodger 16y ago
  Use the node version manager: https://github.com/visionmedia/n https://github.com/visionmedia/n npm install n n 0.4.5 and you're done
- deleted 16y ago
  [deleted]
- auxbuss 16y ago
  Even on ubuntu, I use the github version, thus: Checkout from github: git://github.com/joyent/node.git Now: git checkout v0.4.5 ./configure make sudo make install node -v There are other ways, but this is pretty simple. Note that when you checkout the tag you will be in a detached HEAD state, which is fine, but when you next want to git pull, make sure you checkout master first, then checkout the next tag you require. You can see all tags with: git tag.
- catch23 16y ago
  We use Tim's nvm here. https://github.com/creationix/nvm https://github.com/creationix/nvm Similar to Ruby's rvm.
- nathanwdavis 16y ago
  Use npm (node package manager).
wvl 16y ago
I love node, but can we please stop submitting every minor release? Anyone interested in a minor release is already following node.
- deleted 16y ago
  [deleted]
- dualogy 16y ago
  Well I for one am not interested in 90% of submissions here but like you I have to live with the voting system here to take care of this... and I simply don't read what I'm not interested in. Since GitHub does not notify me satisfactorily about new releases -- "watching" projects gives me a huge noisy stream about all their various activities so a new release gets lost in that stream -- and since twitter.com/nodejs is unfortunately not maintained, YC HN is an outstanding way to get notified about new NodeJS, jQuery etc. releases.
deleted 16y ago
[deleted]
mwill 16y ago
I don't follow V8 version to version, I'm a little bit curious: I notice each node release has a newer V8 version, is this just grabbing a newer version of V8 as a general practice, or is there specific changes in V8 applicable to node? (The may be a question better asked on the google group)

43 points by chapel 16y ago

awesome, but could somebody explain a unix noob on whats the easiest way to update an existing node.js (ubuntu) installation?

olalonde 16y ago
Just install the new version, it will overwrite the previously installed version.
bootload 16y ago
"... the easiest way to update an existing node.js (ubuntu) installation? ..." The latest vid from ryan ~ http://blog.nodejs.org/2011/03/17/welcome-to-the-node-blog/ http://blog.nodejs.org/2011/03/17/welcome-to-the-node-blog/ explained the need to download & install from source. This presumes you have V8 installed. Holler if you get into trouble I've installed a few times on Ubuntu 8.04 Hardy Heron.
- kragen 16y ago
  You mean, he explained that it was necessary to build from source, and why? Is this information available in textual form?
  - bootload 16y ago
    "... You mean, he explained that it was necessary to build from source, and why? Is this information available in textual form? ..." It isn't 100% necessary. You can install from binaries. But as node is a moving target as a dev you get the best feature set/bug fixed version, faster. The talk hasn't been transcribed to my knowledge. Why not view the vid or ask @ryan or irc://irc.freenode.net#freenode why from source? The install instructions here ~ https://github.com/joyent/node/wiki/Installation https://github.com/joyent/node/wiki/Installation or install binaries here ~ https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager https://github.com/joyent/node/wiki/Installing-Node.js-via-p...
- rmg42 16y ago
  Isn't the v8 source included in node and built as part of the build process? deps/v8?
  - bootload 16y ago
    "... Isn't the v8 source included in node: V8 is included in the Node distribution. To use TLS, ..." Yes, right. From v1 (I only looked back to 1) V8 is installed. I install it anyway.
deleted 16y ago
[deleted]
dualogy 16y ago
I have written the following script for this. Update all the version numbers for the next update. Somehow I was too lazy to make this a variable. Downloads the Node TAR.GZ to the current folder and extracts, so put this in some extra folder such as "node_setup". And run the script with sudo. #!/bin/bash apt-get install build-essential g++ curl libssl-dev apache2-utils pkg-config wget http://nodejs.org/dist/node-v0.4.5.tar.gz gunzip node-v0.4.5.tar.gz tar -xf node-v0.4.5.tar cd node-v0.4.5 ./configure make make install
- fullmoon 16y ago
  Just wanted to share a little trick that I like very much curl http://nodejs.org/dist/node-v0.4.5.tar.gz http://nodejs.org/dist/node-v0.4.5.tar.gz | tar -zxvf - -z GZip compressed input -x Extract -v Verbose -f File
selectnull 16y ago
I use ppa: sudo add-apt-repository ppa:jerome-etienne/neoip sudo apt-get update sudo apt-get install nodejs I got 0.4.5 this morning from the usual upgrade, before I even saw the news.
- dualogy 16y ago
  Awesome, I like your approach even better than mine (below). Switched to this but will keep my script for my future users in case they're NodeJS noobs...
- ashchristopher 16y ago
  On 64-bit Ubuntu you will only get 0.2.6 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: nodejs 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 0B/1,834kB of archives. After this operation, 5,349kB of additional disk space will be used. Selecting previously deselected package nodejs. (Reading database ... 57171 files and directories currently installed.) Unpacking nodejs (from .../nodejs_0.2.6~lucid1~ppa201101061407_amd64.deb) ... Setting up nodejs (0.2.6~lucid1~ppa201101061407) ...
rjrodger 16y ago
Use the node version manager: https://github.com/visionmedia/n https://github.com/visionmedia/n npm install n n 0.4.5 and you're done
deleted 16y ago
[deleted]
auxbuss 16y ago
Even on ubuntu, I use the github version, thus: Checkout from github: git://github.com/joyent/node.git Now: git checkout v0.4.5 ./configure make sudo make install node -v There are other ways, but this is pretty simple. Note that when you checkout the tag you will be in a detached HEAD state, which is fine, but when you next want to git pull, make sure you checkout master first, then checkout the next tag you require. You can see all tags with: git tag.
catch23 16y ago
We use Tim's nvm here. https://github.com/creationix/nvm https://github.com/creationix/nvm Similar to Ruby's rvm.
nathanwdavis 16y ago
Use npm (node package manager).

wvl 16y ago

I love node, but can we please stop submitting every minor release? Anyone interested in a minor release is already following node.

deleted 16y ago
[deleted]
dualogy 16y ago
Well I for one am not interested in 90% of submissions here but like you I have to live with the voting system here to take care of this... and I simply don't read what I'm not interested in. Since GitHub does not notify me satisfactorily about new releases -- "watching" projects gives me a huge noisy stream about all their various activities so a new release gets lost in that stream -- and since twitter.com/nodejs is unfortunately not maintained, YC HN is an outstanding way to get notified about new NodeJS, jQuery etc. releases.

deleted 16y ago

[deleted]

mwill 16y ago

I don't follow V8 version to version, I'm a little bit curious: I notice each node release has a newer V8 version, is this just grabbing a newer version of V8 as a general practice, or is there specific changes in V8 applicable to node? (The may be a question better asked on the google group)