Age | Commit message (Collapse) | Author |
|
- chore(docs): remove html from docs build
- feat(docs): migrate new Gatsby site to cli/docs
- chore(docs): fix docs url path
- chore(docs): add new build doc step
- chore(docs): add static linking
- chore(docs): add npm favicon
- chore(docs): update files for tests
- chore(docs): make relative paths absolute
- chore(docs): fix routing on docs dependant tests
- chore(docs): add prepublishOnly docs building step
- chore(docs): add docs/public to .gitignore
- chore(docs): rename dot json markdown files with hyphen names
- chore(docs): clean package.json
- chore(docs): highlight scripts in list
- chore(docs): add strong styles
- chore(docs): fix .json links on markdown
- Added copy to the features page
- Added an install page (copied from existing online docs)
- Added a FeatureLink component to components/links.js
- feat(docs): replace docs sh script with node
- chore(docs): fix docs building process
- chore(docs): docs folder cleanup
PR-URL: https://github.com/npm/cli/pull/274
Credit: @claudiahdz
Close: #274
Reviewed-by: @ruyadorno
|
|
Adds a new config `--format-package-lock`, which defaults to true.
If set to false, then the package lock will be written without any
indentation or line breaks.
PR-URL: https://github.com/npm/cli/pull/248
Credit: @bl00mber
Close: #248
Reviewed-by: @isaacs
Note: squashed and edited slightly for style. -- @isaacs
|
|
PR-URL: https://github.com/npm/cli/pull/90
Credit: @zkat
Reviewed-By: @aeschright
Reviewed-By: @iarna
|
|
Fixes: https://npm.community/t/1327
PR-URL: https://github.com/npm/cli/pull/46
Credit: @SneakyFish5
Reviewed-By: @zkat
|
|
`npm audit` currently exits with exit code 1 if any vulnerabilities are found of any level.
Add a flag of `--audit-level` to `npm audit` to allow it to pass if only vulnerabilities below a certain level are found.
Example: `npm audit --audit-level=high` will exit with 0 if only low or moderate level vulns are detected.
Fixes: https://npm.community/t/245
PR-URL: https://github.com/npm/cli/pull/31
Credit: @lennym
Reviewed-By: @zkat
|
|
Remove publish from list of commands not affected by dry-run
PR-URL: https://github.com/npm/cli/pull/34
Credit: @joebowbeer
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/26
Credit: @dwilches
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/12697
Credit: @tribou
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/20750
Credit: @travi
Reviewed By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/20389
Credit: @iarna
Reviewed-By: @zkat
|
|
This commit adds support for the noProxy configuration.
All whats really needed is passing the option to the `pacote` package,
this will pass it to `make-fetch-happen` and finally to the `request`
package where this is implemented.
Fixes: #18350
Fixes: #7168
PR-URL: https://github.com/npm/npm/pull/19157
Credit: @Saturate
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/19858
Credit: @nalinbhardwaj
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/19870
Credit: @joebowbeer
Reviewed-By: @zkat
|
|
This makes npm follow the NO_COLOR standard, as explained in
http://no-color.org/
> All command-line software which outputs text with ANSI color added
> should check for the presence of a NO_COLOR environment variable that,
> when present (regardless of its value), prevents the addition of ANSI
> color.
npm already provides environment variables (npm_config_color=false) and
options (--no-color) to disable coloring by default, but NO_COLOR is an
comprehensive approach to disable colors for all tools.
PR-URL: https://github.com/npm/npm/pull/19929
Credit: @chneukirchen
Reviewed-By: @zkat
|
|
|
|
Credit: @bmeck
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/19104
|
|
PR-URL: https://github.com/npm/npm/pull/19160
Credit: @alopezsanchez
Reviewed-By: @iarna
Fixes: https://github.com/npm/npm/issues/18789
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/18372
Credit: @jakubholynet
Reviewed-By: @iarna
|
|
The "notice" loglevel was added and made the default in `npm@5`, but the
docs were not updated to this change. This patch updates the loglevel
docs to the new default and adds "notice" to the list of possible
values.
I don't know how to describe "notice" so I just left it at that.
PR-URL: https://github.com/npm/npm/pull/18397
Credit: @KenanY
Reviewed-By: @iarna
|
|
Credit: @isaacs
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/16804
|
|
PR-URL: https://github.com/npm/npm/pull/17142
Credit: @faazshift
Reviewed-By: @iarna
|
|
where it states PEM included Windows naming as (Windows calls it "Base-64 encoded X.509 (.CER)")
PR-URL: https://github.com/npm/npm/pull/17785
Credit: @lgp1985
Reviewed-By: @zkat
|
|
Fixes: https://github.com/npm/npm/issues/6543
PR-URL: https://github.com/npm/npm/pull/16687
Credit: @mmkal
Reviewed-By: @zkat
Reviewed-By: @iarna
|
|
PR-URL: https://github.com/npm/npm/pull/17074
Credit: @KennethKinLum
Reviewed-By: @iarna
|
|
PR-URL: https://github.com/npm/npm/pull/17075/files
Credit: @KennethKinLum
Reviewed-By: @iarna
|
|
Credit: @racztiborzoltan
Reviewed-By: @KenanY
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/17369
|
|
|
|
|
|
|
|
|
|
Fixes: #11342
PR-URL: https://github.com/npm/npm/pull/16213
Credit: @lucastheisen
Reviewed-By: @iarna
|
|
|
|
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
|
|
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
|
|
Fixes: #12529
Credit: @iarna
Reviewed-By: @othiym23
|
|
Credit: @tuhoojabotti
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/14546
|
|
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
|
|
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
|
|
PR-URL: https://github.com/npm/npm/pull/13911
Credit: @othiym23
Reviewed-By: @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
|
|
With the older version of gauge (and thus the older version of npmlog), if
you didn't have a tty then `gauge.enable` was ignored. This is no longer
the case, so now we need to do tty detection before enabling it ourselves.
As a bonus, this now means tty detection is done exactly the same way for
the progress bar as it is for color.
PR-URL: https://github.com/npm/npm/pull/13075
Credit: @iarna
|
|
"cert" and "key" wording uses the same structure as "ca" wording.
Credit: @rvedotrc
PR-URL: https://github.com/npm/npm/pull/12415
|
|
Credit: @rvedotrc
PR-URL: https://github.com/npm/npm/pull/12415
|
|
PR-URL: https://github.com/npm/npm/pull/11666
Credit: @misterbyrne
Reviewed-By: @iarna
|