documentation
documentation copied to clipboard
npm
Documentation for the npm registry, website, and command-line interface.
~~Add explanation on how to safely set local `NPM_TOKEN` environment variable.~~ ~~The current documentation instructs to use local `NPM_TOKEN` environment variable with `docker build --build-arg NPM_TOKEN=${NPM_TOKEN} .` command which is...
The current content of the [Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file#required-name-and-version-fields) page indicates that the `"name"` and `"version"` fields are always required > A `package.json` file must contain `"name"` and `"version"` fields....
# What / Why Non-index pages for the npm CLI docs do not currently redirect to the “default” version when omitting the version number (e.g., https://docs.npmjs.com/cli/commands/npx). Because of this, no...
# What / Why  ## When Scroll down to the section `description` (*not* `Description` above) ## Where https://docs.npmjs.com/cli/v7/configuring-npm/package-json ## How URLs don't care about casing so the HTML anchor...
# What / Why > The package name guideline does not seem to mention that the package name cannot contain capital letters. Should it be added to the guidelines? I'll...
# What / Why Current documentation is lacking and doesn't have details about doing this entire flow from npmjs.com (only talks about the CLI. We should fix this! ## When...
When creating JS libraries, the [`package.json` documentation](https://docs.npmjs.com/cli/v7/configuring-npm/package-json) on docs.npmjs.com is one of the most helpful resources to me. However it is far from complete, there are many fields that aren't...
# What / Why Apparently many `package.json` vars have been removed since v6 ([reference](https://github.com/npm/cli/issues/2609)). But docs are still pointing to them [here](https://docs.npmjs.com/cli/v8/using-npm/scripts#packagejson-vars): > You can access these variables in your...
# What / Why `content/packages-and-modules/getting-packages-from-the-registry/searching-for-and-choosing-packages-to-download.mdx` is outdated. `npm` no longer uses `npms` for scoring. And there is no up-to-date information on how `npm` is scoring packages anywhere. ## Where https://docs.npmjs.com/searching-for-and-choosing-packages-to-download
# What / Why The package-lock.json file contains a property called `requires`: ```jsonc { "name": "foo", "version": "0.0.0", "lockfileVersion": 3, "requires": true, //
