Age | Commit message (Collapse) | Author |
|
PR-URL: https://github.com/npm/npm/pull/9929
|
|
When running `install --save` in a folder with a shrinkwrap that has
dev-only dependencies in it, it's important that we don't then throw
away the dev dependencies just because they didn't say
`install --save --also=dev`.
PR-URL: https://github.com/npm/npm/pull/9992
Fixes: #9647
|
|
PR-URL: https://github.com/npm/npm/pull/9982
|
|
PR-URL: https://github.com/npm/npm/pull/9982
|
|
PR-URL: https://github.com/npm/npm/pull/9954
|
|
If an optional dependency was not installed, shrinkwrap fails with a
message saying that a required dependency is missing. This patch checks
whether a missing dependency was listed in the optionalDependencies.
PR-URL: https://github.com/npm/npm/pull/9879
|
|
the NODE_ENV.
The following is the condition of setting the value of the development / production option.
npm install
+ dev: true
+ prod: true
--only=dev
+ dev: true
+ prod: false
--only=prod || NODE_ENV=production
+ dev: false
+ prod: true
PR-URL: https://github.com/npm/npm/pull/9835
Fixes: #9463
|
|
PR-URL: //github.com/npm/npm/pull/9890
Fixes: #9766
|
|
PR-URL: //github.com/npm/npm/pull/9890
Fixes: #9766
|
|
Bring consistent guarding against null/undefined and consistent
business logic.
PR-URL: //github.com/npm/npm/pull/9890
Fixes: #9766
|
|
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/9471
|
|
PR-URL: https://github.com/npm/npm/pull/9667
|
|
PR-URL: https://github.com/npm/npm/pull/9741
|
|
PR-URL: https://github.com/npm/npm/pull/9744
Fixes: #9695
|
|
PR-URL: https://github.com/npm/npm/pull/9558
|
|
|
|
|
|
Some test leaves a node_modules folder in test/tap and that makes
this test fail. =/
|
|
PR-URL: https://github.com/npm/npm/pull/9537
Fixes: 9394
|
|
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/9409
|
|
PR-URL: https://github.com/npm/npm/pull/9369
Fixes: #9308
|
|
PR-URL: https://github.com/npm/npm/pull/9367
Fixes: #9205
|
|
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
|
|
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.
|
|
PR-URL: https://github.com/npm/npm/pull/9011
|
|
PR-URL: https://github.com/npm/npm/pull/9011
|
|
PR-URL: https://github.com/npm/npm/pull/9011
|
|
PR-URL: https://github.com/npm/npm/pull/9198
|
|
Fixes: #9223
PR-URL: https://github.com/npm/npm/pull/9261
|
|
PR-URL: https://github.com/npm/npm/pull/9024
|
|
PR-URL: https://github.com/npm/npm/pull/9024
|
|
PR-URL: https://github.com/npm/npm/pull/9024
|
|
PR-URL: https://github.com/npm/npm/pull/9169
|
|
(And removes.)
PR-URL: https://github.com/npm/npm/pull/9167
Fixes: #8871
|
|
|
|
`preversion`, `version`, and `postversion` lifecycle scripts were
getting included in the generic run-script section instead of being
listed as lifecycle events when running `npm run-script` with no
arguments.
Fixes: #9146
PR-URL: https://github.com/npm/REPO/pull/9149
|
|
PR-URL: https://github.com/npm/npm/pull/8985
|
|
PR-URL: https://github.com/npm/npm/pull/9037
Fixes: https://github.com/npm/npm/issues/8704
|
|
This also pushes them off to their own file, so we can stop doing
the copy-pasta dance. It also makes explaining the rational of the
check cleaner I think.
PR-URL: https://github.com/npm/npm/pull/9038
|
|
This does a few things:
1. It fixes the calls to npm-install-checks– we were passing a
read-package-tree node, and it wants package.json data.
2. This moves checks to be at "install" time (resolveWithNewModule), so
they happen earlier.
3. Arguments passed in from the command line are checked even earlier.
This is where "don't install yourself" checks are done.
PR-URL: https://github.com/npm/npm/pull/9039
Fixes: https://github.com/npm/npm/issues/8637
Fixes: https://github.com/npm/npm/issues/8921
|
|
|
|
resource
PR-URL: https://github.com/npm/npm/pull/8974
Fixes: https://github.com/npm/npm/issues/8701
This was breaking things on windows due to locking around the files being
created and removed.
|