Servers don't use a GUI installer :P
Re:Node v4.0.0
by andresmanz on Tuesday September 08, 2015 @03:43PM
(#10187786)
Some do[0], even if they shouldn't.
[0] https://en.m.wikipedia.org/wiki/File:Desktop_on_Windows_Serv...
Re:Node v4.0.0
by Already__Taken on Wednesday September 09, 2015 @05:45AM
(#10190538)
Server core has been an option for maybe 7 years now though.
Use your package manager to update then...
$ cat /etc/issue
Ubuntu 14.04.3 LTS \n \l
$ apt-cache showpkg nodejs | head
Package: nodejs
Versions:
0.10.25~dfsg2-2ubuntu1 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages) (/var/lib/dpkg/status)
My package manager knows nothing of this mythical "bleeding edge" of which you speak...Probably your best bet at this point is to use the NodeSource repos to keep up to date with the latest (stable) versions: https://github.com/nodesource/distributions
Re:Node v4.0.0
by michaelsbradley on Tuesday September 08, 2015 @10:06PM
(#10189275)
Or use nvm: https://github.com/creationix/nvm
`nvm install v4.0.0` and you're ready to go.
To preserve your npm packages, try:
nvm install node --reinstall-packages-from=node
Re:Node v4.0.0
by jaredmcateer on Tuesday September 08, 2015 @11:05PM
(#10189440)
Oh that's super helpful I didn't rtfm enough, thanks for the tip.
If you don't mind fetching package locations over HTTP
nvm maintainer here: the only thing that's done over HTTP is the initial redirect on http://nvm.sh, which will soon be HTTPS. This URL is only used if you type it in (because it's easy to remember).
Everything else is done over Github's super-secure HTTPS - so there's really nothing to be paranoid about.
Ah, thanks for the update
nvm install 4.0 works, do we really need the "v"?
nvm maintainer here: you do not need the `v`, it will always be automatically added if you've provided a version number that doesn't already match to an existing alias.
Since it's the first and only release so far in 4.x.y, I got away with `nvm install 4`. ;)
Using `stable` is also another way.
> nvm install stable
v4.0.0 is already installed.
Now using node v4.0.0 (npm v2.14.2)nvm maintainer here: this is true - but please use `node`, since the concept of "stable" and "unstable" has died with the advent of node v4.0 using semver.
All node versions are now stable, and version numbers now communicate breakage, not stability. As it should be.
...all you have to do is re-install it with the GUI installer and you're good to go
And fix all the incompatible changes in your own code.
Unless of course..you are from iojs
It's backwards compatible and works fine from what I see
Re:Node v4.0.0
by wishinghand on Tuesday September 08, 2015 @06:41PM
(#10188611)
I thought changing the first number in SEMVER means breaking changes?
Mostly what is breaking in Node.js is the underlying v8 APIs. You're generally only broken if you've got a C++ module using these v8 APIs.
Lots of native modules are going to have issues until they are updated.
Re:Node v4.0.0
by therealmarv on Wednesday September 09, 2015 @11:08AM
(#10191897)
this is not true. Had problems with webpack and flux packages on old projects. io.js and node.js 4.x is not always compatible to old 0.12.x node.js !
Re:Node v4.0.0
by KenanSulayman on Tuesday September 08, 2015 @04:08PM
(#10187931)
Node 4 will become a LTS release in October.
For anyone who wants to upgrade either from node 0.12 or iojs 3.30..all you have to do is re-install it with the GUI installer and you're good to go..for your personal computer at least!