| Age | Commit message (Collapse) | Author |
|---|
|
`npm` believe they’ve fixed the `npm update -g` command upstream, and
having tried for an hour today to get my Node installation to break
itself via `npm` it looks like they have.
This ultimately resolves #34413 and related issues, for good, hopefully.
Closes #38717.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Kinda hate doing this so soon after the last Node release, but npm has
disclosed and fixed a couple of reasonably serious security issues in
the 2.7.5 release and we should push that.
See: https://github.com/npm/npm/releases/tag/v2.7.5
Closes #38350.
Signed-off-by: Xu Cheng <xucheng@me.com>
|
|
|
|
Bump.
Closes #38281.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Bump.
Closes #38059.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Both 2.6.1 and the consequent 2.7.0 ended up being really quite major
npm releases, with some nifty new features, not least:
*drumroll* the problem where doing `npm update -g` would completely
murder your entire npm installation has been significantly reduced. Not
completely, but significantly.
Other stuff:
* New documentation pertaining to the above. If you’re super-interested
in running wild with the `npm update -g` command, give the new docs a
glance over first.
* A change to the handling of node-gyp which could make handling iojs
in Homebrew a less painful situation for everyone involved in the near
future.
* Minor internal deps updates.
Revision for the whole making it much harder to kill off your own npm
installation with the `npm update -g` command.
Closes #37443.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Closes #36833.
Closes #36899.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Personally, I’d be content to keep the dep as recommended, but it’s
possible the big red warning on the different build standards is making
people jumpy, and there are use cases where the `icu4c` dep does
interfere with certain usage, so I’ve partially reverted the direction
I took in the Node PR the other day by making the new ICU capabilities
optional.
Also added a caveat for the benefit of clarity, and hope more people
complain to Node upstream to fix the real root cause of the problem
here and make life for packagers a little easier.
Closes #36712.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Shoot me in the arm and colour me surprised, Node 0.12 has landed
stable.
Also bump npm to 2.5.1 - Although marked pre-release by upstream this
is the npm version shipped in this Node release, and currently in iojs
as well, and npm is actively nudging people into deliberately jumping
over the normal release schedule just for once, so following that lead
here.
I’ve also taken the chance to simplify the formula quite a bit,
removing the increasingly complicated devel/head/stable logic and
meshing it back into one easier block. The icu4c dep lands as
recommended because Node upstream are shipping binaries with that
support (in English) available. OpenSSL remains optional, but is moved
to general availability rather than just devel for the sake of
simplification and having it optional everywhere causing no harm.
Deps may need rebuilding. I’m hoping the bot is kind enough to check
the bottles of the formulae that have them, but I’ll do a general
double check ASAP.
Closes #36608.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
This is duplicating work that Homebrew does automatically.
|
|
Closes #36473.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Closes #36280.
Closes #36322.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Closes #36159.
Also includes an npm bump, some audit fixes, a rewording of my previous
OpenSSL notes. We may want to consider an npm revision, but I don’t
think it’s urgent just yet - Nobody has reported any issues updating
between the old 2.1.x branch and the new 2.3.0 branch.
Closes #36222.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Pass a list to ln_sf instead of iterating over the result of Dir[]. This
form raises an error if the second argument is not a directory.
Closes #35973.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Fixes the situation where the links would skew in the event that
man1, man3, man5 and/or man7 didn't exist. This should be pretty rare
unless from a clean system, but this will guard against the failure
at least.
Closes #35969. Closes #35971.
Signed-off-by: Tim D. Smith <git@tim-smith.us>
|
|
I goofed here on the manpage linkage and location. This fixes that
mistake. Given it’s post-install, shouldn’t be any need to regenerate
bottles or such.
Closes #35824.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Bottle the npm make install process to support clt-only installs.
Closes #35341
Closes #35748.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
This reverts commit 84813bdf42a871b5e048e07c78adebeec67b76e1.
|
|
This reverts commit 2520aa3c7fb8bf199fd39f76930d6dcc632c234b.
|
|
|
|
Bottle the npm make install process to better support clt-only
installs.
Closes #35341
Closes #35738.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
An `npm` bump and general formula revision. The latest `npm` squashes a
small bundle of race conditions around git dependencies, so it’d be
good to push this into users’ hands more immediately than the next Node
release, hence the revision.
This essentially follows the new Homebrew Node guidelines of update and
revision big, ignore little, bump whatever is available when there’s a
Node update out.
Also fixes a bug around manpages and weird names causing breakage,
because there are still people out there who prefer to not follow
manpage naming conventions. Whole bundle of other smaller, less
consequential documentation updates.
Closes #35480.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Conflicts:
Library/Formula/node.rb
|
|
|
|
Version bump.
Deals primarily with the issue of Node refusing connections to AWS
services based on untrusted certs as of the last release.
See https://github.com/joyent/node/pull/8904 for detail.
Closes #35223.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
|
|
Closes #35144.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
|
|
An ` npm ` version bump, and bumps the Node links to https because Node
has finally started rocking site-wide SSL/TLS :heart:.
Closes #34708.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
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>
|
