Update "npm" to version 3.7.1 - #18
Closed
marekventur wants to merge 1 commit into
Closed
marekventur wants to merge 1 commit into
marekventur wants to merge 1 commit into
Conversation
|
@marekventur can you please remove or obscure all the @-names in these PRs? I don't want to get pinged forever on a module I'm not involved with just because I contributed something to npm once. |
Owner
Author
|
fair enough, sorry, haven't thought about that. I'll get it done as soon as possible. |
|
thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#3.7.1 / 2016-02-01
This reverts commit 1d1ea7eeb958034878eb6573149aeecc686888d3.
Fixes: #11349
This was causing crashes due to cycles in metadata.
Update "semver" to version 5.1.0 #3.7.0 / 2016-01-29
Update "semver" to version 5.1.0 #3.6.0 / 2016-01-22
Dev dep.
Update makes tests pass w/o sudo and also on @iarna's laptop.
Credit: @iarna
ansi@0.3.1
lodash.pad@3.2.0
lodash.repeat@3.1.0
path-array@1.0.1
array-index@1.0.0
es6-symbol@3.0.2
d@0.1.1
es5-ext@0.10.11
es6-iterator@2.0.0
builtin-modules@1.1.1
ansi@0.3.1
lodash.pad@3.2.0
lodash.repeat@3.1.0
util-extend@1.0.3
bl@1.0.1
async@1.5.2
har-validator@2.0.6
escape-string-regexp@1.0.4
is-my-json-valid@2.12.4
sshpk@1.7.3
dashdash@1.12.2
tweetnacl@0.13.3
mime-types@2.1.9
mime-db@1.21.0
spdx-correct@1.0.2
spdx-license-ids@1.2.0
spdx-expression-parse@1.0.2
spdx-exceptions@1.0.4
spdx-license-ids@1.2.0
brace-expansion@1.1.2
Credit: @jdalton
Credit: @jdalton
Credit: @jdalton
Credit: @jdalton
Credit: @jdalton
Bug fixes, including the non-linear performance that previously was biting npm.
Credit: @jdalton
You can pass in arguments to node and nyc now‼
Credit: @isaacs
Update tests for most recent version of ini
Credit: @dominictarr
Previously if any of the npm controlled paths had an ENOENT then we would
return fales from
isEverInside– not an error condition, but a failed match.What we actually want to do is ONLY do that if ALL of the paths are ENOENT. If
any aren't, then we want to test them normally.
PR-URL: A collection of patches necessary for prerelease versions of node to pass the test suite npm/npm#11212
Credit: @iarna
Reviewed-By: @othiym23
That is, previously some tests were running child npm's with from-scratch
environments. Instead this makes it build on what
common-npmputtogether, making changes to that. We need this because we needed a way for
common-npmto suppress warnings about prerelease versions of node.PR-URL: A collection of patches necessary for prerelease versions of node to pass the test suite npm/npm#11212
Credit: @iarna
Reviewed-By: @othiym23
PR-URL: A collection of patches necessary for prerelease versions of node to pass the test suite npm/npm#11212
Credit: @iarna
Reviewed-By: @othiym23
PR-URL: A collection of patches necessary for prerelease versions of node to pass the test suite npm/npm#11212
Credit: @iarna
Reviewed-By: @othiym23
PR-URL: A collection of patches necessary for prerelease versions of node to pass the test suite npm/npm#11212
Credit: @iarna
Reviewed-By: @othiym23
PR-URL: Add my changelog generator tool npm/npm#11077
Credit: @iarna
Reviewed-By: ¯_(ツ)_/¯
Reviewed-By: @othiym23
PR-URL: doc: briefly explain what's included in
npm publishnpm/npm#11188Credit: @beaugunderson
Reviewed-By: @othiym23
Previously, installed packages that contained node_modules with a .bin
directory woudn't get cleaned up correctly. After unbuild of that particular
package, npm would complain with ENOENT errors because the package directory
would be empty (without package.json), as it only contains the leftover
node_modules/.bindirectory.PR-URL: Fix uninstall leaving nested modules directories with .bin npm/npm#11181
Credit: @chrisirhc
Reviewed-By: @othiym23
Fixes: #10887
Fixes: #10938
npm sets node_config_node_gyp without quotes, so its usage should be
quoted. Indeed, it is a better practice to define environment variables
that contain paths without quotes and quote their usage.
PR-URL: windows: fix custom node-gyp env var quoting npm/npm#11158
Credit: @orangemocha
Reviewed-By: @othiym23
--depth Infinityinstead of--depth 9999PR-URL: doc: advise use of
--depth Infinityinstead of--depth 9999npm/npm#11150Credit: @halhenke
Reviewed-By: @othiym23
Previously, correctMkdir() would cache the results early within its
operation (after the stat, before calling chownr) meaning that any second
call would immediately return the cached results, before the earlier chownr
finishes. This causes a race condition where the initial chownr would fail
with ENOENT (or similar errors) trying to scan files that were being
actively created/deleted/etc by the install process. The fix guards the
whole correctMkdir function with inflight() so that multiple calls do not do
chownr simultaneously nor return early. It would also be reasonable to not
cache the results until after the chownr has finished, however that would
still lead to an even more subtle race condition, so the guard on the whole
call is required.
PR-URL: install: fix race condition correcting cache directory ownership npm/npm#11142
Credit: @Jimbly
Reviewed-By: @othiym23
The programmatic
npmAPI is unsupported, and is not guaranteed not to break in non-major versions.Removing this section so newcomers aren't encouraged to discover or use it.
PR-URL: nuke "using npm programmatically" section npm/npm#11130
Credit: @ljharb
Reviewed-By: @othiym23
Credit: @orangejulius
Reviewed-By: @othiym23
PR-URL: Add link to Local Paths section npm/npm#11128
PR-URL: outdated: report symlinked packages as 'linked' npm/npm#11115
Credit: @halhenke
Reviewed-By: @othiym23
Fixes: #8752
Credit: @ashleygwilliams
Reviewed-By: @othiym23
PR-URL: doc: fix 3.5.4 release date in CHANGELOG.md npm/npm#11090
writeFileAtomic is not atomic in Windows, it fails if the file is
being accessed concurrently.
Fixes: #7885
Fixes: #9696
PR-URL: cache: ignore failures replacing package.json npm/npm#10940
Credit: @orangemocha
Reviewed-By: @othiym23
PR-URL: Add a success message to adduser/login npm/npm#10903
Fixes: #10775
Credit: @ekmartin
Reviewed-By: @othiym23
It might be helpful to remind people that they're trying to run
a script before they actually run
npm installon the package.PR-URL: Implement reminder if using run/run-script without 'install' npm/npm#10043
Credit: @timkrins
PR-URL: Add 'npm version from-git' npm/npm#10717
Credit: @ekmartin
PR-URL: Add 'npm version from-git' npm/npm#10717
Credit: @ekmartin
PR-URL: Add 'npm version from-git' npm/npm#10717
Credit: @ekmartin
PR-URL: Add 'npm version from-git' npm/npm#10717
Credit: @ekmartin
Use the --reuseaddr flag when starting the git daemon in tests.
While we can listen to a git server's process shutting down,
there's no guarantee that the socket will have been returned to
the OS by then, so the next server might still get an EADDRINUSE.
PR-URL: test: fix race condition in git tests npm/npm#11127
Credit: @zkat
PR-URL: The repo, as its checked in, has
npm lserrors: npm/npm#11129Credit: @iarna
PR-URL: The repo, as its checked in, has
npm lserrors: npm/npm#11129Credit: @iarna
PR-URL: The repo, as its checked in, has
npm lserrors: npm/npm#11129Credit: @iarna
PR-URL: The repo, as its checked in, has
npm lserrors: npm/npm#11129Credit: @iarna
Update "semver" to version 5.1.0 #3.5.4 / 2016-01-08
Removes deprecated features.
Fixes a host of bugs around dot files in ignores
Credit: @isaacs
Change the default on windows to be false, as international windows installs
often install to non-unicode codepages and there's no way to detect this short of
a system call or a call to a command line program.
Credit: @iarna
New nyc, codecov.io AND coveralls.io support, t.end() multiple times is an error. Better windows support.
Credit: @isaacs
Fixed bug when windows path parts are quoted.
Fixed bug in uid / gid checks.
Credit: @isaacs
Adds ability to disable glob support / pass in options.
Credit: @isaacs
Minor performance improvements
Credit: @calvinmetcalf
Rewrite to use modern streams even on 0.8 plus a bunch of tests
Credit: @iarna
Some bug fixes around large inputs
Credit: @timoxley
PR-URL: Update default value documentation for color variable npm/npm#11044
Credit: @scottaddie
process.installPrefixprocess.installPrefix was removed here:
Drop vestigial
process.installPrefix,node --vars, NODE_CFLAGS and NODE_PREFIX nodejs/node-v0.x-archive#3483. It wasannounced here:
https://github.com/jhnns/node/wiki/API-changes-between-v0.6-and-v0.8.
PR-URL: process.installPrefix was removed as of 0.8.x. npm/npm#10990
Credit: @jeffmcmahan
PR-URL: Correct the name property max length constraint verbiage npm/npm#11037
Credit: @scottaddie
For uniformity with the docs for the "publish" command, use code formatting for tag names in the docs for the "dist-tag" command.
PR-URL: npm-dist-tag docs: Explain why the
latesttag matters npm/npm#10787Credit: @cvrebert
latestis speciallatesttag, by explaining itsspecial significance to
npm install. Currently, only its default statuswith respect to
npm publishis mentioned.npm-the-tool and npm-the-project. The old docs made it sound like the
nexttag might've has special significance to npm-the-tool, when it wasinstead talking about npm-the-project (AFAIK).
not universally known.
PR-URL: npm-dist-tag docs: Explain why the
latesttag matters npm/npm#10787Credit: @cvrebert
publish --tagPR-URL: Link to tag docs in docs for
npm publish --tagnpm/npm#10788Credit: @cvrebert
PR-URL: Gloss 1st prose mention of "tag" in
npm installdocs npm/npm#10789Credit: @cvrebert
That is, that
npm install foo≡npm install foo@latestby defaultPR-URL: Clarify that
npm install foo≡npm install foo@latestby default npm/npm#10790Credit: @cvrebert
Also, clean out the docs and prune the tree before making a release
tarball, to keep as much cruft as possible out of the release tarball.
PR-URL: src: always install in npm in legacy mode npm/npm#10798
Credit: @othiym23