@smithery/api 0.11.0 → 0.13.0

package/oidc/node_modules/npm/docs/content/using-npm/package-spec.md

@@ -1,92 +0,0 @@
----
-title: package-spec
-section: 7
-description: Package name specifier
----
-
-### Description
-
-Commands like `npm install` and the dependency sections in the `package.json` use a package name specifier.
-This can be many different things that all refer to a "package".  Examples include a package name, git url, tarball, or local directory.
-These will generally be referred to as `<package-spec>` in the help output for the npm commands that use this package name specifier.
-
-### Package name
-
-* `[<@scope>/]<pkg>`
-* `[<@scope>/]<pkg>@<tag>`
-* `[<@scope>/]<pkg>@<version>`
-* `[<@scope>/]<pkg>@<version range>`
-
-Refers to a package by name, with or without a scope, and optionally tag, version, or version range.
-This is typically used in combination with the [registry](/using-npm/config#registry) config to refer to a package in a registry.
-
-Examples:
-* `npm`
-* `@npmcli/arborist`
-* `@npmcli/arborist@latest`
-* `npm@6.13.1`
-* `npm@^4.0.0`
-
-### Aliases
-
-* `<alias>@npm:<name>`
-
-Primarily used by commands like `npm install` and in the dependency sections in the `package.json`, this refers to a package by an alias.
-The `<alias>` is the name of the package as it is reified in the `node_modules` folder, and the `<name>` refers to a package name as found in the configured registry.
-
-See `Package name` above for more info on referring to a package by name, and [registry](/using-npm/config#registry) for configuring which registry is used when referring to a package by name.
-
-Examples:
-* `semver:@npm:@npmcli/semver-with-patch`
-* `semver:@npm:semver@7.2.2`
-* `semver:@npm:semver@legacy`
-
-### Folders
-
-* `<folder>`
-
-This refers to a package on the local filesystem.
-Specifically this is a folder with a `package.json` file in it.
-This *should* always be prefixed with a `/` or `./` (or your OS equivalent) to reduce confusion.
-npm currently will parse a string with more than one `/` in it as a folder, but this is legacy behavior that may be removed in a future version.
-
-Examples:
-
-* `./my-package`
-* `/opt/npm/my-package`
-
-### Tarballs
-
-* `<tarball file>`
-* `<tarball url>`
-
-Examples:
-
-* `./my-package.tgz`
-* `https://registry.npmjs.org/semver/-/semver-1.0.0.tgz`
-
-Refers to a package in a tarball format, either on the local filesystem or remotely via url.
-This is the format that packages exist in when uploaded to a registry.
-
-### git urls
-
-* `<git:// url>`
-* `<github username>/<github project>`
-
-Refers to a package in a git repo.
-This can be a full git url, git shorthand, or a username/package on GitHub.
-You can specify a git tag, branch, or other git ref by appending `#ref`.
-
-Examples:
-
-* `https://github.com/npm/cli.git`
-* `git@github.com:npm/cli.git`
-* `git+ssh://git@github.com/npm/cli#v6.0.0`
-* `github:npm/cli#HEAD`
-* `npm/cli#c12ea07`
-
-### See also
-
-* [npm-package-arg](https://npm.im/npm-package-arg)
-* [scope](/using-npm/scope)
-* [config](/using-npm/config)

package/oidc/node_modules/npm/docs/content/using-npm/registry.md

@@ -1,61 +0,0 @@
----
-title: registry
-section: 7
-description: The JavaScript Package Registry
----
-
-### Description
-
-To resolve packages by name and version, npm talks to a registry website that implements the CommonJS Package Registry specification for reading package info.
-
-npm is configured to use the **npm public registry** at
-<https://registry.npmjs.org> by default.
-Use of the npm public registry is subject to terms of use available at <https://docs.npmjs.com/policies/terms>.
-
-You can configure npm to use any compatible registry you like, and even run your own registry.
-Use of someone else's registry may be governed by their terms of use.
-
-npm's package registry implementation supports several write APIs as well, to allow for publishing packages and managing user account information.
-
-The registry URL used is determined by the scope of the package (see [`scope`](/using-npm/scope).
-If no scope is specified, the default registry is used, which is supplied by the [`registry` config](/using-npm/config#registry) parameter.
-See [`npm config`](/commands/npm-config), [`npmrc`](/configuring-npm/npmrc), and [`config`](/using-npm/config) for more on managing npm's configuration.
-Authentication configuration such as auth tokens and certificates are configured specifically scoped to an individual registry.
-See [Auth Related Configuration](/configuring-npm/npmrc#auth-related-configuration)
-
-When the default registry is used in a package-lock or shrinkwrap it has the special meaning of "the currently configured registry". If you create a lock file while using the default registry you can switch to another registry and npm will install packages from the new registry, but if you create a lock file while using a custom registry packages will be installed from that registry even after you change to another registry.
-
-### Does npm send any information about me back to the registry?
-
-Yes.
-
-When making requests of the registry npm adds two headers with information about your environment:
-
-* `Npm-Scope` – If your project is scoped, this header will contain its scope.
-In the future npm hopes to build registry features that use this information to allow you to customize your experience for your organization.
-* `Npm-In-CI` – Set to "true" if npm believes this install is running in a continuous integration environment, "false" otherwise.
-This is detected by looking for the following environment variables: `CI`, `TDDIUM`,
-  `JENKINS_URL`, `bamboo.buildKey`.
-If you'd like to learn more you may find the [original PR](https://github.com/npm/npm-registry-client/pull/129) interesting.
-  This is used to gather better metrics on how npm is used by humans, versus build farms.
-
-The npm registry does not try to correlate the information in these headers with any authenticated accounts that may be used in the same requests.
-
-### How can I prevent my package from being published in the official registry?
-
-Set `"private": true` in your `package.json` to prevent it from being published at all, or
-`"publishConfig":{"registry":"http://my-internal-registry.local"}`
-to force it to be published only to your internal/private registry.
-
-See [`package.json`](/configuring-npm/package-json) for more info on what goes in the package.json file.
-
-### Where can I find my (and others') published packages?
-
-<https://www.npmjs.com/>
-
-### See also
-
-* [npm config](/commands/npm-config)
-* [config](/using-npm/config)
-* [npmrc](/configuring-npm/npmrc)
-* [npm developers](/using-npm/developers)

package/oidc/node_modules/npm/docs/content/using-npm/removal.md

@@ -1,55 +0,0 @@
----
-title: removal
-section: 7
-description: Cleaning the Slate
----
-
-### Synopsis
-
-So sad to see you go.
-
-```bash
-sudo npm uninstall npm -g
-```
-
-Or, if that fails, please proceed to more severe uninstalling methods.
-
-### More Severe Uninstalling
-
-Usually, the above instructions are sufficient.
-That will remove npm, but leave behind anything you've installed.
-
-If that doesn't work, or if you require more drastic measures, continue reading.
-
-Note that this is only necessary for globally-installed packages.
-Local installs are completely contained within a project's `node_modules` folder.
-Delete that folder, and everything is gone unless a package's install script is particularly ill-behaved.
-
-This assumes that you installed node and npm in the default place.
-If you configured node with a different `--prefix`, or installed npm with a different prefix setting, then adjust the paths accordingly, replacing
-`/usr/local` with your install prefix.
-
-To remove everything npm-related manually:
-
-```bash
-rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*
-```
-
-If you installed things *with* npm, then your best bet is to uninstall them with npm first, and then install them again once you have a proper install.
-This can help find any symlinks that are lying around:
-
-```bash
-ls -laF /usr/local/{lib/node{,/.npm},bin,share/man} | grep npm
-```
-
-Prior to version 0.3, npm used shim files for executables and node modules.
-To track those down, you can do the following:
-
-```bash
-find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;
-```
-
-### See also
-
-* [npm uninstall](/commands/npm-uninstall)
-* [npm prune](/commands/npm-prune)

package/oidc/node_modules/npm/docs/content/using-npm/scope.md

@@ -1,123 +0,0 @@
----
-title: scope
-section: 7
-description: Scoped packages
----
-
-### Description
-
-All npm packages have a name.
-Some package names also have a scope.
-A scope follows the usual rules for package names (URL-safe characters, no leading dots or underscores).
-When used in package names, scopes are preceded by an `@` symbol and followed by a slash, e.g.
-
-```bash
-@somescope/somepackagename
-```
-
-Scopes are a way of grouping related packages together, and also affect a few things about the way npm treats the package.
-
-Each npm user/organization has their own scope, and only you can add packages in your scope.
-This means you don't have to worry about someone taking your package name ahead of you.
-Thus it is also a good way to signal official packages for organizations.
-
-Scoped packages can be published and installed as of `npm@2` and are supported by the primary npm registry.
-Unscoped packages can depend on scoped packages and vice versa.
-The npm client is backwards-compatible with unscoped registries, so it can be used to work with scoped and unscoped registries at the same time.
-
-### Installing scoped packages
-
-Scoped packages are installed to a sub-folder of the regular installation folder, e.g. if your other packages are installed in `node_modules/packagename`, scoped modules will be installed in `node_modules/@myorg/packagename`.
-The scope folder (`@myorg`) is simply the name of the scope preceded by an `@` symbol, and can contain any number of scoped packages.
-
-A scoped package is installed by referencing it by name, preceded by an
-`@` symbol, in `npm install`:
-
-```bash
-npm install @myorg/mypackage
-```
-
-Or in `package.json`:
-
-```json
-"dependencies": {
-  "@myorg/mypackage": "^1.3.0"
-}
-```
-
-Note that if the `@` symbol is omitted, in either case, npm will instead attempt to install from GitHub; see [`npm install`](/commands/npm-install).
-
-### Requiring scoped packages
-
-Because scoped packages are installed into a scope folder, you have to include the name of the scope when requiring them in your code, e.g.
-
-```javascript
-require('@myorg/mypackage')
-```
-
-There is nothing special about the way Node treats scope folders.
-This simply requires the `mypackage` module in the folder named `@myorg`.
-
-### Publishing scoped packages
-
-Scoped packages can be published from the CLI as of `npm@2` and can be published to any registry that supports them, including the primary npm registry.
-
-(As of 2015-04-19, and with npm 2.0 or better, the primary npm registry
-**does** support scoped packages.)
-
-If you wish, you may associate a scope with a registry; see below.
-
-#### Publishing public scoped packages to the primary npm registry
-
-Publishing to a scope, you have two options:
-
-- Publishing to your user scope (example: `@username/module`)
-- Publishing to an organization scope (example: `@org/module`)
-
-If publishing a public module to an organization scope, you must first either create an organization with the name of the scope that you'd like to publish to or be added to an existing organization with the appropriate permissions.
-For example, if you'd like to publish to `@org`, you would  need to create the `org` organization on npmjs.com prior to trying to publish.
-
-Scoped packages are not public by default.
-You will need to specify
-`--access public` with the initial `npm publish` command.
-This will publish the package and set access to `public` as if you had run `npm access public` after publishing.
-You do not need to do this when publishing new versions of an existing scoped package.
-
-#### Publishing private scoped packages to the npm registry
-
-To publish a private scoped package to the npm registry, you must have an [npm Private Modules](https://docs.npmjs.com/private-modules/intro) account.
-
-You can then publish the module with `npm publish` or `npm publish
---access restricted`, and it will be present in the npm registry, with restricted access.
-You can then change the access permissions, if desired, with `npm access` or on the npmjs.com website.
-
-### Associating a scope with a registry
-
-Scopes can be associated with a separate registry.
-This allows you to seamlessly use a mix of packages from the primary npm registry and one or more private registries, such as [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org) project.
-
-You can associate a scope with a registry at login, e.g.
-
-```bash
-npm login --registry=http://reg.example.com --scope=@myco
-```
-
-Scopes have a many-to-one relationship with registries: one registry can host multiple scopes, but a scope only ever points to one registry.
-
-You can also associate a scope with a registry using `npm config`:
-
-```bash
-npm config set @myco:registry=http://reg.example.com
-```
-
-Once a scope is associated with a registry, any `npm install` for a package with that scope will request packages from that registry instead.
-Any
-`npm publish` for a package name that contains the scope will be published to
-that registry instead.
-
-### See also
-
-* [npm install](/commands/npm-install)
-* [npm publish](/commands/npm-publish)
-* [npm access](/commands/npm-access)
-* [npm registry](/using-npm/registry)

package/oidc/node_modules/npm/docs/content/using-npm/scripts.md

@@ -1,350 +0,0 @@
----
-title: scripts
-section: 7
-description: How npm handles the "scripts" field
----
-
-### Description
-
-The `"scripts"` property of your `package.json` file supports a number of built-in scripts and their preset life cycle events as well as arbitrary scripts.
-These all can be executed by running `npm run <stage>`.
-*Pre* and *post* commands with matching names will be run for those as well (e.g.
-`premyscript`,
-`myscript`, `postmyscript`).
-Scripts from dependencies can be run with `npm explore <pkg> -- npm run <stage>`.
-
-### Pre & Post Scripts
-
-To create "pre" or "post" scripts for any scripts defined in the
-`"scripts"` section of the `package.json`, simply create another script
-*with a matching name* and add "pre" or "post" to the beginning of them.
-
-```json
-{
-  "scripts": {
-    "precompress": "{{ executes BEFORE the `compress` script }}",
-    "compress": "{{ run command to compress files }}",
-    "postcompress": "{{ executes AFTER `compress` script }}"
-  }
-}
-```
-
-In this example `npm run compress` would execute these scripts as described.
-
-### Life Cycle Scripts
-
-There are some special life cycle scripts that happen only in certain situations.
-These scripts happen in addition to the `pre<event>`, `post<event>`, and
-`<event>` scripts.
-
-* `prepare`, `prepublish`, `prepublishOnly`, `prepack`, `postpack`, `dependencies`
-
-**prepare** (since `npm@4.0.0`)
-* Runs BEFORE the package is packed, i.e.
-during `npm publish` and `npm pack`
-* Runs on local `npm install` without any arguments
-* Runs AFTER `prepublish`, but BEFORE `prepublishOnly`
-* Runs for a package if it's being installed as a link through `npm install <folder>`
-
-* NOTE: If a package being installed through git contains a `prepare` script, its `dependencies` and `devDependencies` will be installed, and the prepare script will be run, before the package is packaged and installed.
-
-* As of `npm@7` these scripts run in the background.
-  To see the output, run with: `--foreground-scripts`.
-
-**prepublish** (DEPRECATED)
-* Does not run during `npm publish`, but does run during `npm ci` and `npm install`.
-See below for more info.
-
-**prepublishOnly**
-* Runs BEFORE the package is prepared and packed, ONLY on `npm publish`.
-
-**prepack**
-* Runs BEFORE a tarball is packed (on "`npm pack`", "`npm publish`", and when installing a git dependency).
-* NOTE: "`npm run pack`" is NOT the same as "`npm pack`". "`npm run pack`" is an arbitrary user defined script name, whereas, "`npm pack`" is a CLI defined command.
-
-**postpack**
-* Runs AFTER the tarball has been generated but before it is moved to its final destination (if at all, publish does not save the tarball locally)
-
-**dependencies**
-* Runs AFTER any operations that modify the `node_modules` directory IF changes occurred.
-* Does NOT run in global mode
-
-#### Prepare and Prepublish
-
-**Deprecation Note: prepublish**
-
-Since `npm@1.1.71`, the npm CLI has run the `prepublish` script for both `npm publish` and `npm install`, because it's a convenient way to prepare a package for use (some common use cases are described in the section below).
-It has also turned out to be, in practice, [very confusing](https://github.com/npm/npm/issues/10074).
-As of `npm@4.0.0`, a new event has been introduced, `prepare`, that preserves this existing behavior.
-A _new_ event, `prepublishOnly` has been added as a transitional strategy to allow users to avoid the confusing behavior of existing npm versions and only run on `npm publish` (for instance, running the tests one last time to ensure they're in good shape).
-
-See <https://github.com/npm/npm/issues/10074> for a much lengthier justification, with further reading, for this change.
-
-**Use Cases**
-
-If you need to perform operations on your package before it is used, in a way that is not dependent on the operating system or architecture of the target system, use a `prepublish` script.
-This includes tasks such as:
-
-* Compiling CoffeeScript source code into JavaScript.
-* Creating minified versions of JavaScript source code.
-* Fetching remote resources that your package will use.
-
-The advantage of doing these things at `prepublish` time is that they can be done once, in a single place, thus reducing complexity and variability.
-Additionally, this means that:
-
-* You can depend on `coffee-script` as a `devDependency`, and thus your users don't need to have it installed.
-* You don't need to include minifiers in your package, reducing the size for your users.
-* You don't need to rely on your users having `curl` or `wget` or other system tools on the target machines.
-
-#### Dependencies
-
-The `dependencies` script is run any time an `npm` command causes changes to the `node_modules` directory.
-It is run AFTER the changes have been applied and the `package.json` and `package-lock.json` files have been updated.
-
-### Life Cycle Operation Order
-
-#### [`npm cache add`](/commands/npm-cache)
-
-* `prepare`
-
-#### [`npm ci`](/commands/npm-ci)
-
-* `preinstall`
-* `install`
-* `postinstall`
-* `prepublish`
-* `preprepare`
-* `prepare`
-* `postprepare`
-
-These all run after the actual installation of modules into
- `node_modules`, in order, with no internal actions happening in between
-
-#### [`npm diff`](/commands/npm-diff)
-
-* `prepare`
-
-#### [`npm install`](/commands/npm-install)
-
-These also run when you run `npm install -g <pkg-name>`
-
-* `preinstall`
-* `install`
-* `postinstall`
-* `prepublish`
-* `preprepare`
-* `prepare`
-* `postprepare`
-
-If there is a `binding.gyp` file in the root of your package and you haven't defined your own `install` or `preinstall` scripts, npm will default the `install` command to compile using node-gyp via `node-gyp rebuild`
-
-These are run from the scripts of `<pkg-name>`
-
-#### [`npm pack`](/commands/npm-pack)
-
-* `prepack`
-* `prepare`
-* `postpack`
-
-#### [`npm publish`](/commands/npm-publish)
-
-* `prepublishOnly`
-* `prepack`
-* `prepare`
-* `postpack`
-* `publish`
-* `postpublish`
-
-#### [`npm rebuild`](/commands/npm-rebuild)
-
-* `preinstall`
-* `install`
-* `postinstall`
-* `prepare`
-
-`prepare` is only run if the current directory is a symlink (e.g.
-with linked packages)
-
-#### [`npm restart`](/commands/npm-restart)
-
-If there is a `restart` script defined, these events are run; otherwise,
-`stop` and `start` are both run if present, including their `pre` and `post` iterations)
-
-* `prerestart`
-* `restart`
-* `postrestart`
-
-#### [`npm run <user defined>`](/commands/npm-run)
-
-* `pre<user-defined>`
-* `<user-defined>`
-* `post<user-defined>`
-
-#### [`npm start`](/commands/npm-start)
-
-* `prestart`
-* `start`
-* `poststart`
-
-If there is a `server.js` file in the root of your package, then npm will default the `start` command to `node server.js`.
-`prestart` and `poststart` will still run in this case.
-
-#### [`npm stop`](/commands/npm-stop)
-
-* `prestop`
-* `stop`
-* `poststop`
-
-#### [`npm test`](/commands/npm-test)
-
-* `pretest`
-* `test`
-* `posttest`
-
-#### [`npm version`](/commands/npm-version)
-
-* `preversion`
-* `version`
-* `postversion`
-
-#### A Note on a lack of [`npm uninstall`](/commands/npm-uninstall) scripts
-
-While npm v6 had `uninstall` lifecycle scripts, npm v7 does not.
-Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful.
-
-
-Reasons for a package removal include:
-
-* a user directly uninstalled this package
-* a user uninstalled a dependent package and so this dependency is being uninstalled
-* a user uninstalled a dependent package but another package also depends on this version
-* this version has been merged as a duplicate with another version
-* etc.
-
-Due to the lack of necessary context, `uninstall` lifecycle scripts are not implemented and will not function.
-
-### Working Directory for Scripts
-
-Scripts are always run from the root of the package folder, regardless of what the current working directory is when `npm` is invoked.
-This means your scripts can reliably assume they are running in the package root.
-
-If you want your script to behave differently based on the directory you were in when you ran `npm`, you can use the `INIT_CWD` environment variable, which holds the full path you were in when you ran `npm run`.
-
-#### Historical Behavior in Older npm Versions
-
-For npm v6 and earlier, scripts were generally run from the root of the package, but there were rare cases and bugs in older versions where this was not guaranteed.
-If your package must support very old npm versions, you may wish to add a safeguard in your scripts (for example, by checking process.cwd()).
-
-For more details, see:
-- [npm v7 release notes](https://github.com/npm/cli/releases/tag/v7.0.0)
-- [Discussion about script working directory reliability in npm v6 and earlier](https://github.com/npm/npm/issues/12356)
-
-### User
-
-When npm is run as root, scripts are always run with the effective uid and gid of the working directory owner.
-
-### Environment
-
-Package scripts run in an environment where many pieces of information are made available regarding the setup of npm and the current state of the process.
-
-#### path
-
-If you depend on modules that define executable scripts, like test suites, then those executables will be added to the `PATH` for executing the scripts.
-So, if your package.json has this:
-
-```json
-{
-  "name" : "foo",
-  "dependencies" : {
-    "bar" : "0.1.x"
-  },
-  "scripts": {
-    "start" : "bar ./test"
-  }
-}
-```
-
-then you could run `npm start` to execute the `bar` script, which is exported into the `node_modules/.bin` directory on `npm install`.
-
-#### package.json vars
-
-The package.json fields are tacked onto the `npm_package_` prefix.
-So, for instance, if you had `{"name":"foo", "version":"1.2.5"}` in your package.json file, then your package scripts would have the `npm_package_name` environment variable set to "foo", and the `npm_package_version` set to "1.2.5".  You can access these variables in your code with `process.env.npm_package_name` and `process.env.npm_package_version`, and so on for other fields.
-
-See [`package.json`](/configuring-npm/package-json) for more on package configs.
-
-#### current lifecycle event
-
-Lastly, the `npm_lifecycle_event` environment variable is set to whichever stage of the cycle is being executed.
-So, you could have a single script used for different parts of the process which switches based on what's currently happening.
-
-Objects are flattened following this format, so if you had
-`{"scripts":{"install":"foo.js"}}` in your package.json, then you'd see this in the script:
-
-```bash
-process.env.npm_package_scripts_install === "foo.js"
-```
-
-### Examples
-
-For example, if your package.json contains this:
-
-```json
-{
-  "scripts" : {
-    "install" : "scripts/install.js",
-    "postinstall" : "scripts/install.js"
-  }
-}
-```
-
-then `scripts/install.js` will be called for the install and post-install stages of the lifecycle.
-Since `scripts/install.js` is running for two different phases, it would be wise in this case to look at the 
-`npm_lifecycle_event` environment variable.
-
-If you want to run a make command, you can do so.
-This works just fine:
-
-```json
-{
-  "scripts" : {
-    "preinstall" : "./configure",
-    "install" : "make && make install",
-    "test" : "make test"
-  }
-}
-```
-
-### Exiting
-
-Scripts are run by passing the line as a script argument to `/bin/sh` on POSIX systems or `cmd.exe` on Windows.
-You can control which shell is used by setting the [`script-shell`](/using-npm/config#script-shell) configuration option.
-
-If the script exits with a code other than 0, then this will abort the process.
-
-Note that these script files don't have to be Node.js or even JavaScript programs.
-They just have to be some kind of executable file.
-
-### Best Practices
-
-* Don't exit with a non-zero error code unless you *really* mean it.
-  If the failure is minor or only will prevent some optional features, then it's better to just print a warning and exit successfully.
-* Try not to use scripts to do what npm can do for you.
-Read through [`package.json`](/configuring-npm/package-json) to see all the things that you can specify and enable by simply describing your package appropriately.
-In general, this will lead to a more robust and consistent state.
-* Inspect the env to determine where to put things.
-For instance, if the `npm_config_binroot` environment variable is set to `/home/user/bin`, then don't try to install executables into `/usr/local/bin`.
-The user probably set it up that way for a reason.
-* Don't prefix your script commands with "sudo".  If root permissions are required for some reason, then it'll fail with that error, and the user will sudo the npm command in question.
-* Don't use `install`.
-Use a `.gyp` file for compilation, and `prepare` for anything else.
-You should almost never have to explicitly set a preinstall or install script.
-If you are doing this, please consider if there is another option.
-The only valid use of `install` or `preinstall` scripts is for compilation which must be done on the target architecture.
-
-### See Also
-
-* [npm run](/commands/npm-run)
-* [package.json](/configuring-npm/package-json)
-* [npm developers](/using-npm/developers)
-* [npm install](/commands/npm-install)