10 ms·

This is crazy fast shipment..almost scary that you have to start keeping up with all the changes.. For anyone who wants to upgrade either from node 0.12 or ioj

• Aldo_MX 11y ago
  Servers don't use a GUI installer :P
  • andrewpe 11y ago
    Use your package manager to update then...
    • csense 11y ago
      $ 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...
      • mscdex 11y ago
        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 https://github.com/nodesource/distributions
        • michaelsbradley 11y ago
          Or use nvm: https://github.com/creationix/nvm https://github.com/creationix/nvm
  • andresmanz 11y ago
    Some do[0], even if they shouldn't. [0] https://en.m.wikipedia.org/wiki/File:Desktop_on_Windows_Server_2016.png https://en.m.wikipedia.org/wiki/File:Desktop_on_Windows_Serv...
    • Already__Taken 11y ago
      Server core has been an option for maybe 7 years now though.
• collyw 11y ago
  ...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.
  • outpost 11y ago
    Unless of course..you are from iojs
  • gedy 11y ago
    It's backwards compatible and works fine from what I see
    • wishinghand 11y ago
      I thought changing the first number in SEMVER means breaking changes?
      • iends 11y ago
        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.
    • mattkrea 11y ago
      Lots of native modules are going to have issues until they are updated.
    • therealmarv 11y ago
      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 !
• KenanSulayman 11y ago
  Node 4 will become a LTS release in October.
  • mAritz 11y ago
    No, the first LTS release is planned for October.
• cornedor 11y ago
  `nvm install v4.0.0` and you're ready to go.
  • ausjke 11y ago
    nvm install 4.0 works, do we really need the "v"?
    • qubyte 11y ago
      Since it's the first and only release so far in 4.x.y, I got away with `nvm install 4`. ;)
      • srn_ 11y ago
        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)
        • ljharb 11y ago
          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.
    • ljharb 11y ago
      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.
  • webXL 11y ago
    To preserve your npm packages, try: nvm install node --reinstall-packages-from=node
    • jaredmcateer 11y ago