| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
This is what happens as a result of the changes to `fstream-npm` -- when
you try to integrate npm downstream, those files won't be there more
because `make release` calls `npm pack`, which uses `fstream-npm`.
PR-URL: https://github.com/npm/npm/pull/9476
|
|
PR-URL: https://github.com/npm/npm/pull/9431
|
|
Add t.contains() as alias to t.match(), and switch to version of `same`
that supports cycles in the object graph.
|
|
Correct a bad README example, and update to newest `json-pointer`.
|
|
|
|
|
|
Add `discard` method to ditch unwanted tar entries.
|
|
Support new version of `validate-npm-package-license`.
|
|
Support `silent` to suppress all output from the init process.
|
|
Reports of `EISDIR` on the issue tracker are almost exclusively caused by users
trying to install something that does not have a `package.json`. However, it is
clearly difficult for many users to discern this simple problem from the error
code alone. So let's expand upon it.
PR-URL: https://github.com/npm/npm/pull/9396
|
|
Followup-To: https://github.com/npm/npm/issues/1648
Fixes: https://github.com/npm/npm/issues/8517
PR-URL: https://github.com/npm/npm/pull/9409
PR-URL: https://github.com/npm/npm/pull/8841
|
|
PR-URL: https://github.com/npm/npm/pull/9409
|
|
PR-URL: https://github.com/npm/npm/pull/9409
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/9386
|
|
PR-URL: https://github.com/npm/npm/pull/9360
|
|
Followup-To: https://github.com/npm/npm/pull/9279
PR-URL: https://github.com/npm/npm/pull/9315
|
|
|
|
|
|
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/9369
Fixes: #9308
|
|
PR-URL: https://github.com/npm/npm/pull/9367
Fixes: #9205
|
|
To make debugging of lifecycle scripts easier
PR-URL: https://github.com/npm/npm/pull/9227
|
|
tap->nyc->yargs added a bunch of new deps that we now need to ignore
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The install order is determined by:
1) The location of the thing to be installed relative to the root module.
2) Dependency order, such that a -> b -> c will install modules as: c, b, a
1 is deterministic, regardless of what's being installed.
But 2 can change the order of things higher in the dep tree. Eg, b, or a
might get sorted earlier if c requires them. This mostly doesn't matter,
but it does mean that if you have two modules with conflicting bins, they
_can_ get installed in different orders. This changes sorts all of the top
level modules to be LAST, in location order (1), and then sorts all the rest
per (2). This ensures that top level modules have a deterministic install
order. (Non top level modules can't have bin conflicts as that's treated
the same as a version conflict and the conflicting module would be hoisted.)
PR-URL: https://github.com/npm/npm/pull/9274
Fixes: #8995
|
|
logical tree
PR-URL: https://github.com/npm/npm/pull/9344
Fixes: #9113
|
|
Previously I was using the path of the module to be updated. But no, silly,
we want the path that CONTAINS it.
PR-URL: https://github.com/npm/npm/pull/9303
Fixes: #9095
|
|
PR-URL: https://github.com/npm/npm/pull/9343
Fixes: #9113
|
|
We have special code to disable the progress bar on travis (and other CI) to
save ourselves and our users a lot of unhelpful output. Unfortunately as
this test didn't take that into account, it immediately exploded in this
envs.
So we fix that up, PLUS we add tests for the various env options for
suppressing progress bars.
PR-URL: https://github.com/npm/npm/pull/9304
|
|
|
|
This changes npm.cmd and the npm script when running in Cygwin to look
for an npm installation in prefix, running it if found. The default npm
is used to get the prefix. This implements the changes described in
https://github.com/joyent/node/issues/8528 .
Fixes joyent/node#8528. Reference: joyent/node#8554.
Fixes: #6412
PR-URL: https://github.com/npm/npm/pull/9089
|
|
/d disables cmd.exe AutoRuns feature, where registry entry points to the
script that will be executed when cmd.exe starts. Surprisingly a lot of
users hase "CD \" or similar command there which causes lifecycle
scripts to fail, since relative path to the script no longer works (and
package.json has no way to deduce absolute path)
/s enables handling of quotes, so that you can have "C:\Program
Files\Node\node.exe" quoted in your script. Node's child_process.exec()
is doing the same. We prevent additional quoting by libuv already by
setting uv_spawn() flag UV_PROCESS_WINDOWS_VERBATIM_ARGUMENTS.
If those flags are not set there is no way package.json can reliably
tell us to run "node" executable with a relative script path:
"scripts": {
"install": "node scripts/install.js"
}
Without /d "node" invocation may end up in a random directory as a
result of the AutoRuns command.
Fixes: #8751
Fixes: #7333
PR-URL: https://github.com/npm/npm/pull/9245
|
|
This reverts commit 8b58ad09b719295461167a34f666c5aa4d6e26f2.
As it turned out, those partial docs aren't actually used by the
http://docs.npmjs.com site, so there's no sense slowing down the build.
PR-URL: https://github.com/npm/npm/pull/9201
|
|
Don't bundle config cruft and project-specific config on publish.
PR-URL: https://github.com/npm/fstream-npm/pull/12
|
|
npm@1.x didn't include configuration values prefixed with an underscore
in the environment passed to chiled processes. npm@2.x includes the
notion of scoped configuration, where a nerfed URL can be used to prefix
configuration, some of which might be underscore-prefixed without the
scope. Add that behavior to npm@2 and close this regression.
PR-URL: https://github.com/npm/npm/pull/9348
|
|
I really don't like it when all my tags start being prefixed with q.
Also reformatted test.
|
|
|
|
|
|
|
|
|
