| Age | Commit message (Collapse) | Author | 
 | 
 | 
 | 
 | 
 | 
Closes #31914.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Okay, this is part 1 of what will likely become a host of wider changes
I propose on Node to tackle the issues discussed in
[#31777](https://github.com/Homebrew/homebrew/issues/31777).
Part 1: I’ve killed the devel build. It hasn’t been updated since May,
and Node haven’t expressed any sort of haste in issuing even a new
minor bump to the devel build that fixes the rather large [OpenSSL
vulnerabilities](https://github.com/joyent/node/tree/v0.11.13-release/de
ps/openssl/openssl) in 0.11.13. At this point, my feeling is that it’s
dangerously irresponsible to leave the devel build present given those
vulnerabilities, and I’d like to see us scrap it until we see some
movement on patching those issues. This issue is open with Node
[here](https://github.com/joyent/node/issues/8000) but remains largely
ignored and dormant.
Second change: Bumps the npm version that we ship back to the latest
stable release. A minor thing, but an early step towards fixing some of
the bigger npm problems.
Third change: Changes the way we handle npm updates post-install to
specifically target the latest stable release. Our current ``` npm
update npm -g ``` has been habitually dumping people onto the alpha &
beta builds for npm, and this solution (according to the npm team)
should solve that problem permanently. Having done local testing with
this, It does indeed seem to do the job.
These are largely minor fixes to patch things over in a stable, solid
fashion till I can work out ways to avoid the Node issues we’ve been
encountering so rampantly lately.
 | 
 | 
Closes #31708.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Updates Node to 0.10.31. I've also switched the npm download to HTTPS because npm support that now (Although Node doesn't, which is weird).
 | 
 | 
This reverts commit b859a5c6a2f8fdf1c660844a8d47a321b8ddea84.
 | 
 | 
Closes #31538.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Closes #31334.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Closes #31286.
 | 
 | 
Closes #31301.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
 | 
 | 
 | 
 | 
Closes #31273.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
 | 
 | 
Closes #30307.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
 | 
 | 
References #29138.
 | 
 | 
Closes #28908.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
fixes conflicting npm pages after pouring a bottle
Closes #28908
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Install npm to the expected location using the upstream tarball. This
should make everyone happier.
Closes #27479.
 | 
 | 
 | 
 | 
Fixes #27683.
 | 
 | 
Closes #27481.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
 | 
 | 
Marking this requirement as recommended eliminates a conditional in the
class body that otherwise breaks `brew upgrade node` for users using
"--without-npm".
Renaming it allows Homebrew to generate the correct option name.
Fixes #26858.
 | 
 | 
Closes #26832.
Signed-off-by: Brett Koonce <koonce@gmail.com>
 | 
 | 
 | 
 | 
Closes #26691.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Closes #26483.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Closes #26419.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
Closes #26254.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
 | 
 | 
Closes #26134.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
 | 
 | 
Closes #25336.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
 | 
 | 
 | 
 | 
Fixes #25294.
 | 
 | 
Closes #25218.
Signed-off-by: Misty De Meo <mistydemeo@gmail.com>
 | 
 | 
Closes #24552.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
 | 
 | 
Fixes #22397.
 | 
 | 
 | 
 | 
Closes #24231.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
 | 
 | 
 | 
 | 
Closes #22951.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
 | 
 | 
 | 
 | 
 | 
 | 
Closes #22316.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
 | 
 | 
Closes #22322.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
 |