Age | Commit message (Collapse) | Author |
|
ci (#4666)
related to #4664
|
|
|
|
|
|
This also allows logs-max to be set to 0 to disable log file writing.
Closes #4466
Closes #4206
|
|
Adds a minimalistic reify step that updates the installed tree after a
version change within one of the configured workspaces when using any
of the workspaces config options.
It's also possible to use the `--save` config option in order to
auto update semver ranges of dependencies declarations accross dependent
`package.json` files.
Fixes: https://github.com/npm/cli/issues/3403
Relates to: https://github.com/npm/rfcs/issues/556
Relates to: https://github.com/npm/cli/issues/3757
Relates to: https://github.com/npm/cli/issues/4193
|
|
Also add explanation of what `--force` does for unpublish
|
|
|
|
|
|
|
|
I think this gets them all
|
|
|
|
Closes #4189
* docs: auto-generate synopsis sections
* feat: improve usage auto-generation'
* chore: auto-generate npm usage for each command
* docs: print default usage when usage is missing
* docs: add special case for npx
* fix: remove optional chaining
|
|
|
|
Closes: https://github.com/npm/cli/issues/3821
|
|
|
|
npm install <folder> doesn't install dependencies if <folder> is outside of root project.
Fixes #3358
|
|
Signed-off-by: Tierney Cyren <hello@bnb.im>
|
|
Fixes https://github.com/npm/cli/issues/4136
|
|
|
|
|
|
`npm ci` should never be affected by the `package-lock` config.
Fixes: https://github.com/npm/cli/issues/4185
|
|
This has been possible since this commit in `npm-bundled`:
https://github.com/npm/npm-bundled/commit/101a94db5953e508b57de0e7b887964691d2d326
|
|
Previously `npm update` was not respecting the `save` option, it
would be impossible for users to use `npm update` and automatically
update their `package.json` files.
This fixes it by adding extra steps on `Arborist.reify._saveIdealTree`
to read direct dependencies of any `package.json` and update them as
needed when reifying using the `update` and `save` options.
- Uses config.isDefault to set a different value for the `save` config
for both the update and dedupe commands
- Tweaks arborist to make sure saveIdealTree preserves the behavior of
skipping writing to package-lock.json on save=false for install while
still writing the lockfile for `npm update` with its new default value
of save=false.
- Updated and added some new tests on arborist to cover for these tweaks
- Added `npm update --save` smoke test on cli
Fixes: https://github.com/npm/cli/issues/708
Fixes: https://github.com/npm/cli/issues/2704
Relates to: https://github.com/npm/feedback/discussions/270
|
|
PR-URL: https://github.com/npm/cli/pull/4092
Credit: @nlf
Close: #4092
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4114
Credit: @lukekarrys
Close: #4114
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4113
Credit: @darcyclarke
Close: #4113
Reviewed-by: @lukekarrys
|
|
PR-URL: https://github.com/npm/cli/pull/4089
Credit: @yotamselementor
Close: #4089
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4081
Credit: @idleberg
Close: #4081
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4072
Credit: @chalkygames123
Close: #4072
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4053
Credit: @MansurAliKoroglu
Close: #4053
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4009
Credit: @danielcobo
Close: #4009
Reviewed-by: @wraithgar
|
|
As all CLI input is considered to be string, eg. a
"npm install --lockfile-version 3" would fail with the error messages:
```
npm WARN invalid config lockfile-version="3" set in command line options
npm WARN invalid config Must be one of: null, 1, 2, 3
```
Until we have a config system that supports setting type and possible values
of configs, we have to specify all string and number values for the
`lockfile-version`, but we coerce all values to numbers in the flattener.
Co-authored-by: @voxpelli
Co-authored-by: @isaacs
PR-URL: https://github.com/npm/cli/pull/3949
Credit: @lukekarrys
Close: #3949
Reviewed-by: @isaacs
|
|
Adds a new config item that includes the workspace root. This also changes
--workspaces to a trinary, so that setting it to false will explicitly exclude
workspaces altogether.
PR-URL: https://github.com/npm/cli/pull/3890
Credit: @fritzy
Close: #3890
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3878
Credit: @XhmikosR
Close: #3878
Reviewed-by: @wraithgar
|
|
Depends on @npmcli/arborist@4.0.0
Re: https://github.com/npm/rfcs/pull/434
PR-URL: https://github.com/npm/cli/pull/3880
Credit: @isaacs
Close: #3880
Reviewed-by: @wraithgar
|
|
This reverts commit f17dfa0ced7d8df9bb7baf378bb20d33175c8e8b.
|
|
Adds a new config item that includes the workspace root when running
non-arborist commands (i.e. repo, version, publish). Arborist will need
to be udpated to look for this flag to change its behavior to include
the workspace root for its functions.
This also changes --workspaces to a trinary, so that setting it to false
will explicitly exclude workspaces altogether. This is also going to
require an arborist change so that it ignores workspaces altogether.
Co-author: @fritzy
PR-URL: https://github.com/npm/cli/pull/3816
Credit: @isaacs
Close: #3816
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3699
Credit: @behnammodi
Close: #3699
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3805
Credit: @ethomson
Close: #3805
Reviewed-by: @lukekarrys
|
|
This behavior has been present in npm for a while, but I haven't found
where it's documented. This is my attempt at documenting the behavior
based on my understanding of it. I think a SME should contribute to this
so the documentation is correct.
npm/feedback#544
npm/cli#3783
https://github.com/npm/arborist/blob/478871bf0a44a8ec516b9057585b8707e60b0349/lib/arborist/reify.js#L687-L693
PR-URL: https://github.com/npm/cli/pull/3784
Credit: @everett1992
Close: #3784
Reviewed-by: @wraithgar
|
|
See npm/documentation#36
PR-URL: https://github.com/npm/cli/pull/3759
Credit: @nategreen
Close: #3759
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3715
Credit: @Matsuuu
Close: #3715
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3690
Credit: @tripu
Close: #3690
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3681
Credit: @fritzy
Close: #3681
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3630
Credit: @austincho
Close: #3630
Reviewed-by: @wraithgar
EDIT(@isaacs): rebased and edited to put config documentation in the
correct location.
|
|
This should prevent the kind of thing we've seen where people edit the
generated docs, as in #3654 and #3630, and provide them with a helpful
pointer so they put the config documentation changes in the right place.
|
|
The content in this portion of the docs is auto-generated.
PR-URL: https://github.com/npm/cli/pull/3654
Credit: @wraithgar
Close: #3654
Reviewed-by: @nlf
|
|
PR-URL: https://github.com/npm/cli/pull/3630
Credit: @austincho
Close: #3630
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3621
Credit: @AkiJoey
Close: #3621
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3523
Credit: @DemiraDimitrova
Close: #3523
Reviewed-by: @wraithgar
|