| Age | Commit message (Collapse) | Author |
|---|
|
PR-URL: https://github.com/npm/npm/pull/16818
Credit: @ankon
Reviewed-By: @zkat
|
|
Ref: https://github.com/npm/npm/blob/v5.0.0/lib/utils/tar.js#L106-L107
PR-URL: https://github.com/npm/npm/pull/16799
Credit: @sonicdoe
Reviewed-By: @zkat
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This introduces changes to how `file:` specifiers work. Specifically, they
now create symlinks.
|
|
|
|
|
|
Fixes: #11342
PR-URL: https://github.com/npm/npm/pull/16213
Credit: @lucastheisen
Reviewed-By: @iarna
|
|
Credit: @famousgarkin
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/16267
|
|
Credit: @desfero
PR-URL: https://github.com/npm/npm/pull/16296
Reviewed-By: @iarna
|
|
|
|
* Mention the 24-hour restriction on unpublish
As detailed in http://blog.npmjs.org/post/141905368000/changes-to-npms-unpublish-policy
* Clarify that 24 hr unpublish policy only applies to default registry
PR-URL: https://github.com/npm/npm/pull/15833
Credit: @carols10cents
Reviewed-By: @zkat
|
|
Previously it defaulted to the global registry, now it will
default to whatever your default registry is.
Credit: @iarna
PR-URL: https://github.com/npm/npm/pull/15757
|
|
PR-URL: https://github.com/npm/npm/pull/13389
Credit: @zkat
Reviewed-By: @iarna
|
|
* doc: fix typo in lib/fetch-package-metadata.md
* doc: replace http://opensource.org with https in doc/files/package.json.md
PR-URL: https://github.com/npm/npm/pull/15539
Credit: @watilde
Reviewed-By: @iarna
|
|
PR-URL: https://github.com/npm/npm/pull/15520
Fixes: https://github.com/npm/docs/issues/795
Credit: @hzoo
Reviewed-By: @iarna
|
|
as per the discussion in [1], clarify the fact that unscoped packages
can depend on scoped packages (and *vice versa*), contrary to
the initial proposal and announcements.
also:
- s/un-scoped/unscoped/ as per e.g. [2]
- fix typos + minor cosmetic tweaks
[1] https://github.com/npm/npm/issues/15305#issuecomment-272599537
[2] https://github.com/npm/npm/blob/v4.1.1/doc/cli/npm-access.md
PR-URL: https://github.com/npm/npm/pull/15480
Credit: @chocolateboy
Reviewed-By: @iarna
|
|
PR-URL: https://github.com/npm/npm/pull/15481
Credit: @zkat
Reviewed-By: @iarna
Reviewed-By: @bcoe
|
|
We also are storing a configurable number of previous log files.
PR-URL: https://github.com/npm/npm/pull/11439
Fixes: #5252
Fixes: #6350
Fixes: #1548
Fixes: #7614
Credit: @KenanY
Credit: @othiym23
Credit: @isaacs
Credit: @iarna
|
|
PR-URL: https://github.com/npm/npm/pull/15235
Credit: @othiym23
Reviewed-By: @iarna
|
|
This command will diagnose user's environment and let
the user know some recommended solutions if they
potentially have any problems related to npm.
Credit: @watilde
Reviewed-By: @othiym23
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/14582
Fixes: #6756
|
|
PR_URL: https://github.com/npm/npm/pull/15157
Credit: @JonahMoses
Reviewed-By: @watilde
Reviewed-By: @iarna
|
|
Fixes: #12529
Credit: @iarna
Reviewed-By: @othiym23
|
|
PR-URL: https://github.com/npm/npm/pull/14559
Credit: @iarna
Reviewed-By: @othiym23
|
|
Credit: @tuhoojabotti
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/14546
|
|
Credit: @strugee
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/14472
|
|
The dispute policy at https://www.npmjs.com/policies/disputes is the
current version of the dispute policy. This syncs up the dispute policy
document here to match what's on the site.
Fixes: #13302
PR-URL: https://github.com/npm/npm/pull/14406
Credit: @mike-engel
Reviewed-By: @iarna
|
|
This updates the two GitHub URL examples that used to be projects under the `visionmedia` organization and uses the current URLs for those projects.
PR-URL: https://github.com/npm/npm/pull/14609
Credit: @dougwilson
Reviewed-By: @iarna
|
|
Fixes: #14479
Credit: @iarna
PR-URL: https://github.com/npm/npm/pull/14519
Reviewed-By: @othiym23
|
|
PR-URL: https://github.com/npm/npm/pull/14501
Credit: @zkat
Reviewed-By: @othiym23
|
|
Credit: @SimenB
PR-URL: https://github.com/npm/npm/pull/14380
Reviewed-By: @zkat
|
|
Credit: @iarna
PR-URL: https://github.com/npm/npm/pull/14129
Reviewed-By: @ashleygwilliams
|
|
Npm-Scope is set to the scope of the current top level project.
Credit: @iarna
PR-URL: https://github.com/npm/npm/pull/14129
Reviewed-By: @othiym23
|
|
Folks should be using the `dist-tag` command now.
Fixes: #6274
PR-URL: https://github.com/npm/npm/pull/14328
Credit: @iarna
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/14290
Credit: @zkat
Reviewed-By: @othiym23
|
|
Now all we have to remember to do is come back to this when we put out
`npm@5`.
PR-URL: https://github.com/npm/npm/pull/14290
Credit: @othiym23
Reviewed-By: @watilde
Reviewed-By: @iarna
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/14329
Credit: @iarna
Reviewed-By: @zkat
|
|
Change the default behaviour of npm to never prepending the
current node executable’s directory to `PATH` but printing a warning
in the cases in which it previously did.
PR-URL: https://github.com/npm/npm/pull/13409
Credit: @addaleax
Reviewed-By: @zkat
Reviewed-By: @othiym23
|
|
Add a `--scripts-prepend-node-path` option that controls `npm`’s
behaviour with respect to adding the directory of
the current `node` executable to the `PATH`, even if that means
that `npm` will invoke a different `node` executable than the
one which it is running.
This is a non-invasive solution to some of the problems described in
https://github.com/npm/npm/issues/12318. It should not come with
any drawbacks for npm’s side, as it shifts the responsibility of
making sure that the `PATH` variable contains everything it should
to whoever invoked npm with `--scripts-prepend-node-path=false`.
While https://github.com/npm/npm/pull/12968 may have addressed some
of the problems described there, it does not help in the case that
the `PATH` has explicitly been overridden with the intention of
having a different `node` executed.
[squash] test: anticipate coverage tooling possibly setting --scripts-prepend-node-path
As one of the motivations for introducing `--scripts-prepend-node-path`
is that `spawn-wrap` (which npm itself uses for coverage) can make use
of that option, anticipate that change in order to not break the
test suite when updating that dependency at a later point.
[squash] tests for scripts-prepend-node-path=auto
[squash] implement `warn-only` setting for `--scripts-prepend-node-path`
Adds a setting that is basically equivalent to `--scripts-prepend-node-path=false`
but emits a warning informing the user about the existence of the
option in the cases in which `npm` currently modifies `PATH`,
as sometimes that’s in the user’s interest.
[squash] fixup tests for windows
PR-URL: https://github.com/npm/npm/pull/13409
Credit: @addaleax
Reviewed-By: @zkat
Reviewed-By: @othiym23
|
|
Credit: @zkat
PR-URL: https://github.com/npm/npm/pull/13746
Reviewed-By: @othiym23
|
|
Credit: @stevokk
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/13904
|
|
PR-URL: https://github.com/npm/npm/pull/13911
Credit: @othiym23
Reviewed-By: @zkat
|
|
Credit: @zkat
|
|
Document that the per-user config file respects the `$NPM_CONFIG_USERCONFIG` env var, defaulting to ~/.npmrc
PR-URL: https://github.com/npm/npm/pull/13493
Credit: @jasonkarns
Reviewed-By: @iarna
|
|
Running 'npm install --save-dev' will update shrinkwrap file, but only
if there already are any dev dependencies in this file.
Fixes: #11735
PR-URL: https://github.com/npm/npm/pull/13860
Credit: @szimek
Reviewed-By: @iarna
|
