| Age | Commit message (Collapse) | Author |
|---|
|
Bumps [yaml](https://github.com/eemeli/yaml) from 1.10.2 to 2.1.1.
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](https://github.com/eemeli/yaml/compare/v1.10.2...v2.1.1)
---
updated-dependencies:
- dependency-name: yaml
dependency-type: direct:development
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
* add instruction to query objects with npm view
* fix package version in example command in npm-view docs
|
|
|
|
|
|
BREAKING CHANGE: the default `auth-type` config value is now `web`
|
|
* docs: add hash to "tag" config link
Minor change.
[using-npm/config](https://docs.npmjs.com/cli/v8/using-npm/config) is a long page -- heck, the subtitle is "More than you probably want to know about npm configuration" -- so instead of dumping people at the top of it when they follow the link to learn about the "tag" config, let's send 'em right to the relevant bit.
Aside from it being a long page, one more motivation: trying to get to the section by searching is also slow, it's the 16th (of 24) occurrence of "tag" on the page. (though to be fair, only the 4th if they catch it in the table of contents)
* docs: fix some nonstandard formatting
* docs: more useful link
Co-authored-by: Luke Karrys <luke@lukekarrys.com>
|
|
|
|
docs: modify Misleading doc about bins
closes #3788
|
|
|
|
The difference between `adduser` and `login` depends on the `auth-type`.
- `web`: the POST to `/-/v1/login` contains a `{ create: true }` value
in its payload for `adduser`
- `legacy` the `PUT` request to `/-/user/org.couchdb.user:${username}`
contains an `email` value in its payload for `adduser`.
BREAKING CHANGE: `login`, `adduser`, and `auth-type` changes
- This removes all `auth-type` configs except `web` and `legacy`.
- `login` and `adduser` are now separate commands that send different data to the registry.
- `auth-type` config values `web` and `legacy` only try
their respective methods, npm no longer tries them all and waits to see
which one doesn't fail.
|
|
|
|
|
|
Corrects grammar (previously said `other’s`).
|
|
BREAKING CHANGE: renames most of the `npm access` subcommands
- `edit`, having never been implemented, is removed
- `public` is now `set status=public`
- `restricted` is now `set status=private`
- `ls-packages` is now `list packages`
- `ls-collaborators` is now `list collaborators`
- `2fa-required` is now `set mfa=publish`
- `2fa-not-required` is now `set mfa=none`
- `set mfa=automation` is added
- output is no longer in json by default
Usage:
npm access list packages [<user>|<scope>|<scope:team> [<package>]
npm access list collaborators [<package> [<user>]]
npm access get status [<package>]
npm access set status=public|private [<package>]
npm access set mfa=false|publish|automation [<package>]
npm access grant <read-only|read-write> <scope:team> [<package>]
npm access revoke <scope:team> [<package>]
Options:
[--json] [--otp <otp>] [--registry <registry>]
|
|
|
|
BREAKING CHANGE: all workspace packages are now compatible with the
following semver range for node: `^14.17.0 || ^16.13.0 || >=18.0.0`
|
|
* docs: remove duplicate description for `prepare` script
* Stylistic change to be consistent
|
|
|
|
BREAKING CHANGE: this changes the default value of `install-links` to
true
Closes https://github.com/npm/statusboard/issues/510
|
|
|
|
Also increase docs tests so they dont timeout when
rebuilding cmark-gfm
|
|
|
|
|
|
|
|
|
|
|
|
fix: correct link to dependency selectors
|
|
* [dependency-selectors] fix example in docs
* Add async to the function declaration because awaits are used
|
|
#5309 will turn it back on
|
|
|
|
|
|
|
|
Fix link syntax in `dependency-selectors.md`
|
|
Lots of bugfixes here, we properly parse ranges and versions, and we
also now work with git repos and gists, and know when they are already
installed.
|
|
feat: add --replace-registry-host=<npmjs|always|never>|<hostname>
|
|
Co-authored-by: Gar <gar+gh@danger.computer>
|
|
Use the full proper name of Travis CI
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|
* docs: describe implicit workspace and prefix configuration
* Update docs/content/using-npm/workspaces.md
Co-authored-by: Gar <gar+gh@danger.computer>
Co-authored-by: Luke Karrys <luke@lukekarrys.com>
Co-authored-by: Gar <gar+gh@danger.computer>
|
|
|
|
|
|
|
|
* docs: update commit-ish default branch
To match with https://github.com/npm/cli/blob/latest/docs/content/using-npm/developers.md#what-is-a-package
|
|
arborist normalizes `bundledDependencies` to `bundleDependencies`, this change corrects the documentation to match that reality
|
|
fix: Update docs for audit signatures cmd
Update command documentation for `npm audit signatures` added in this PR:
https://github.com/npm/cli/pull/4827
|
|
Closes #4765
RFC: https://github.com/npm/rfcs/pull/591
While this doesn't directly allow top-level cert/key as credentials (per the
original issue), it's a more targeted/secure approach that accomplishes the
same end-result; the new options are scoped to a specific registry, and the
actual cert/key contents are much less likely to be exposed. See the RFC for
more context.
Depends on:
* https://github.com/npm/npm-registry-fetch/pull/125
* https://github.com/npm/config/pull/69
|
|
|
|
|
|
|
|
The use of `a` workspace have some inconsistency in terms of naming, making the doc not easy to follow.
|
