| Age | Commit message (Collapse) | Author |
|---|
|
Removes the devel block. As far as upstream are concerned, the 0.11.x
branch is pretty much done, and won’t receive further dependencies
updates, including OpenSSL. The v0.12 branch, which is our current
HEAD, is the new development branch.
Closes #34527.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Primarily an npm bump. The other element is to deal with some of the
newer HEAD developments available.
Closes #34511.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Closes #34413.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
This is the revision point previously discussed. Roughly every 4 new
npm versions, or any major developments useful to Homebrew. This
qualifies as both, particularly around the cache directory and handling
intentional or unintentional use of sudo.
Closes #34377.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Version bump for npm. 2.19 (the one after this release) is probably a
good point for a general revision, as it deals with some sudo/cache
permission issues that have cropped up semi-regularly.
Closes #34182.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Primarily an npm bump, sans revision because the one minor version bump
isn’t worth a revision for even with our new policy. Other than that,
fixes the HEAD to actually point at the main development stream,
depreciates the enable option, adds another line of note to the OpenSSL
situation, and slightly rewords the caveat to clarify the npm install
situation.
Closes #34084.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
This change avoids setting 'loglevel' in the npm builtin npmrc file.
Setting the log level to 'verbose' is intended only for the postinstall
step and is not desired to be persistent.
Closes #33756.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Closes #33618.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Also: run `make install`, unlink any leftover manpages, set log level to
verbose, don't install the latest version of npm, don't link manpages
(as npm now does that itself).
|
|
Closes #33524.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Version bump, and merging in some of the changes from #33017.
|
|
Closes #33599.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
In case the PATH isn't setup correctly by users.
|
|
|
|
Node have finally released a devel build that isn’t vulnerable to the
last 8 months of OpenSSL bugs, so we can throw that back in. In
addition they’ve started releasing the SHA256 checksums of each package
alongside the SHA1, Progress!
Closes #32623.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
Closes #32372.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
|
|
|
|
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>
|
