Hi All, This is happening today. Right after the timestamp on this message. If you're reading it after the timestamp, you will need to update your local node install to 4.2.2 (LTS). Or give NVM a shot.
Here's where to get it -- https://nodejs.org/en/download/ For you package manager users out there -- https://nodejs.org/en/download/package-manager/ After updating you *MUST* |make really-clean|. I would also suggest running |npm cache clear|. Please word, --aus On Wed, Nov 11, 2015 at 4:15 PM, Aus Lacroix <[email protected]> wrote: > Hi All, > > As many of you may know, we've been stuck on node 0.12 for quite a long > time. > > Many efforts have gone in to update _the world_ to run node 4.2.2 (LTS). > > See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1223661 if you're > extra curious about what was updated. > > *We will be attempting to land this as soon as the reviews are completed.* > > *I'll let this list know when it's landed*, but, in short, if no tests > run, you probably need to update your version of node and make > really-clean. :) > > nvm (https://github.com/creationix/nvm) provides an interesting toolbox > to deal with multiple versions of node installed locally. I suggest you use > it if you need more than one version present on your system at a time. > > Garent Aye also wrote something called envy that can help manager multiple > node versions. > > I *highly* recommend dealing with this upgrade sooner rather than later. :) > > word, > --aus >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
