| /third_party/node/deps/npm/tap-snapshots/test/lib/ |
| D | npm.js.test.cjs | 8 exports[`test/lib/npm.js TAP usage set process.stdout.columns column width 0 > must match snapshot …
9 npm <command>
13 npm install install all the dependencies in your project
14 npm install <foo> add the <foo> dependency to your project
15 npm test run this project's tests
16 npm run <foo> run the script named <foo>
17 npm <command> -h quick help on <command>
18 npm -l display usage info for all commands
19 npm help <term> search for help on <term>
20 npm help npm more involved overview
[all …]
|
| /third_party/node/deps/npm/test/lib/ |
| D | npm.js | 4 const { load: loadMockNpm } = require('../fixtures/mock-npm.js')
9 const { npm, logs } = await loadMockNpm(t, { load: false })
10 t.match(npm, {
20 t.throws(() => npm.config.set('foo', 'bar'))
21 t.throws(() => npm.config.get('foo'))
25 t.test('npm.load', async t => {
27 const { npm } = await loadMockNpm(t, { load: false })
29 npm.config.load = async () => {
33 () => npm.load(),
37 t.equal(npm.loadErr, loadError)
[all …]
|
| /third_party/node/deps/npm/test/lib/commands/ |
| D | access.js | 3 const { load: loadMockNpm } = require('../../fixtures/mock-npm.js')
16 testComp(['npm', 'access'], ['list', 'get', 'set', 'grant', 'revoke'])
17 testComp(['npm', 'access', 'list'], ['packages', 'collaborators'])
18 testComp(['npm', 'access', 'ls'], ['packages', 'collaborators'])
19 testComp(['npm', 'access', 'get'], ['status'])
20 testComp(['npm', 'access', 'set'], [
30 testComp(['npm', 'access', 'grant'], ['read-only', 'read-write'])
31 testComp(['npm', 'access', 'revoke'], [])
32 testComp(['npm', 'access', 'grant', ''], [])
35 access.completion({ conf: { argv: { remain: ['npm', 'access', 'foobar'] } } }),
[all …]
|
| D | doctor.js | 5 const { load: loadMockNpm } = require('../../fixtures/mock-npm')
17 name: 'npm',
20 name: 'npm',
85 const { joinedOutput, logs, npm } = await loadMockNpm(t, {
90 tnock(t, npm.config.get('registry'))
92 .get('/npm').reply(200, npmManifest(npm.version))
95 await npm.exec('doctor', [])
101 const { joinedOutput, logs, npm } = await loadMockNpm(t, {
109 tnock(t, npm.config.get('registry'))
111 .get('/npm').reply(200, npmManifest(npm.version))
[all …]
|
| D | init.js | 4 const _mockNpm = require('../../fixtures/mock-npm')
27 const { npm, joinedOutput } = await mockNpm(t, {
31 await npm.exec('init', [])
35 t.test('classic npm init -y', async t => {
36 const { npm, prefix } = await mockNpm(t, {
41 await npm.exec('init', [])
48 t.test('classic interactive npm init', async t => {
51 const { npm } = await mockNpm(t, {
55 resolve(npm.localPrefix),
61 await npm.exec('init', [])
[all …]
|
| /third_party/node/deps/npm/docs/content/commands/ |
| D | npm-install.md | 2 title: npm-install
10 npm install [<package-spec> ...]
18 package has a package-lock, or an npm shrinkwrap file, or a yarn lock file,
22 * `npm-shrinkwrap.json`
26 See [package-lock.json](/configuring-npm/package-lock-json) and
27 [`npm shrinkwrap`](/commands/npm-shrinkwrap).
32 [`package.json`](/configuring-npm/package-json) file
36 [`registry`](/using-npm/registry)) with (c)
37 * e) a `<name>@<tag>` (see [`npm dist-tag`](/commands/npm-dist-tag)) that
43 of using npm if you just want to write a node program (a), and perhaps if
[all …]
|
| D | npm-doctor.md | 2 title: npm-doctor
4 description: Check the health of your npm environment
10 npm doctor [ping] [registry] [versions] [environment] [permissions] [cache]
17 `npm doctor` runs a set of checks to ensure that your npm installation has
18 what it needs to manage your JavaScript packages. npm is mostly a
21 + Node.js and git must be executable by npm.
22 + The primary npm registry, `registry.npmjs.com`, or another service that
24 + The directories that npm uses, `node_modules` (both locally and
26 + The npm cache exists, and the package tarballs within it aren't corrupt.
28 Without all of these working properly, npm may not work properly. Many
[all …]
|
| D | npm-init.md | 2 title: npm-init
10 npm init <package-spec> (same as `npx <package-spec>`)
11 npm init <@scope> (same as `npx <@scope>/create`)
18 `npm init <initializer>` can be used to set up a new or existing npm
21 `initializer` in this case is an npm package named `create-<initializer>`,
22 which will be installed by [`npm-exec`](/commands/npm-exec), and then have its
26 The init command is transformed to a corresponding `npm exec` operation as
29 * `npm init foo` -> `npm exec create-foo`
30 * `npm init @usr/foo` -> `npm exec @usr/create-foo`
31 * `npm init @usr` -> `npm exec @usr/create`
[all …]
|
| D | npm.md | 2 title: npm
10 npm
21 npm is the package manager for the Node JavaScript platform. It puts
29 Run `npm help` to get a list of available commands.
33 npm comes preconfigured to use npm's public registry at
34 https://registry.npmjs.org by default. Use of the npm public registry is
38 You can configure npm to use any compatible registry you like, and even
44 You probably got npm because you want to install stuff.
47 program is `npm install` to install its dependencies.
49 You can also run `npm install blerg` to install the latest version of
[all …]
|
| D | npm-cache.md | 2 title: npm-cache
10 npm cache add <package-spec>
11 npm cache clean [<key>]
12 npm cache ls [<name>@<version>]
13 npm cache verify
20 Used to add, list, or clean the npm cache folder.
24 intended to be used internally by npm, but it can provide a way to
29 unnecessary, as npm's cache is self-healing and resistant to data
38 npm stores cache data in an opaque directory within the configured `cache`,
40 [`cacache`](http://npm.im/cacache)-based content-addressable cache that
[all …]
|
| D | npm-pkg.md | 2 title: npm-pkg
10 npm pkg set <key>=<value> [<key>=<value> ...]
11 npm pkg get [<key> [<key> ...]]
12 npm pkg delete <key> [<key> ...]
13 npm pkg set [<array>[<index>].<key>=<value> ...]
14 npm pkg set [<array>[].<key>=<value> ...]
15 npm pkg fix
21 `npm pkg` provide 3 different sub commands that allow you to modify or retrieve
26 same notation used in [`npm view`](/commands/npm-view) to retrieve information
31 * `npm pkg get <field>`
[all …]
|
| D | npm-config.md | 2 title: npm-config
4 description: Manage the npm configuration files
10 npm config set <key>=<value> [<key>=<value> ...]
11 npm config get [<key> [<key> ...]]
12 npm config delete <key> [<key> ...]
13 npm config list [--json]
14 npm config edit
15 npm config fix
24 npm gets its config settings from the command line, environment
27 See [npmrc](/configuring-npm/npmrc) for more information about the npmrc
[all …]
|
| D | npm-start.md | 2 title: npm-start
10 npm start [-- <args>]
18 If the `"scripts"` object does not define a `"start"` property, npm
25 As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
26 use custom arguments when executing scripts. Refer to [`npm run-script`](/commands/npm-run-script) …
39 npm start
41 > npm@x.x.x start
55 If true, npm does not run scripts specified in package.json files.
58 `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run-script`
69 The shell to use for scripts run with the `npm exec`, `npm run` and `npm
[all …]
|
| D | npm-ls.md | 2 title: npm-ls
10 npm ls <package-spec>
22 tree at all, use [`npm explain`](/commands/npm-explain).
27 example, running `npm ls promzard` in npm's source tree will show:
30 npm@10.5.0 /path/to/npm
48 The `npm ls` command's output and behavior made a _ton_ of sense when npm
54 npm v3, the `ls` output was modified to display the logical dependency
56 However, without using `npm ls -l`, it became impossible to show _where_ a
59 With the advent of automatic installation of `peerDependencies` in npm v7,
64 Also, in the years since npm got an `ls` command (in version 0.0.2!),
[all …]
|
| D | npm-exec.md | 2 title: npm-exec
4 description: Run a command from a local or remote npm package
10 npm exec -- <pkg>[@<version>] [args...]
11 npm exec --package=<pkg>[@<version>] -- <cmd> [args...]
12 npm exec -c '<cmd> [args...]'
13 npm exec --package=foo -c '<cmd> [args...]'
20 This command allows you to run an arbitrary command from an npm package
22 as running it via `npm run`.
39 installed to a folder in the npm cache, which is added to the `PATH`
49 are provided, then npm will attempt to determine the executable name from
[all …]
|
| /third_party/skia/modules/pathkit/ |
| D | Makefile | 4 npm: npm-test npm-debug target
5 mkdir -p ./npm-wasm/bin
6 mkdir -p ./npm-asmjs/bin
8 cp ../../out/pathkit/pathkit.js ./npm-wasm/bin
9 cp ../../out/pathkit/pathkit.wasm ./npm-wasm/bin
11 cp ../../out/pathkit/pathkit.js ./npm-asmjs/bin/pathkit.js
12 cp ../../out/pathkit/pathkit.js.mem ./npm-asmjs/bin/pathkit.js.mem
15 cd npm-wasm; npm publish
16 cd npm-asmjs; npm publish
19 cd npm-wasm; npm version major
[all …]
|
| /third_party/node/deps/npm/man/man1/ |
| D | npm-doctor.1 | 1 .TH "NPM-DOCTOR" "1" "February 2024" "" ""
3 \fBnpm-doctor\fR - Check the health of your npm environment
15 \fBnpm doctor\fR runs a set of checks to ensure that your npm installation has what it needs to man…
18 Node.js and git must be executable by npm.
20 The primary npm registry, \fBregistry.npmjs.com\fR, or another service that uses the registry API, …
22 The directories that npm uses, \fBnode_modules\fR (both locally and globally), exist and can be wri…
24 The npm cache exists, and the package tarballs within it aren't corrupt.
28 …y, npm may not work properly. Many issues are often attributable to things that are outside npm's …
30 … many issue reports due to using old versions of npm. Since npm is constantly improving, running \…
32 \fBnpm doctor\fR verifies the following items in your environment, and if there are any recommended…
[all …]
|
| D | npm-init.1 | 1 .TH "NPM-INIT" "1" "February 2024" "" ""
3 \fBnpm-init\fR - Create a package.json file
16 \fBnpm init <initializer>\fR can be used to set up a new or existing npm package.
18 …initializer\fR in this case is an npm package named \fBcreate-<initializer>\fR, which will be inst…
20 The init command is transformed to a corresponding \fBnpm exec\fR operation as follows:
23 \fBnpm init foo\fR -> \fBnpm exec create-foo\fR
25 \fBnpm init @usr/foo\fR -> \fBnpm exec @usr/create-foo\fR
27 \fBnpm init @usr\fR -> \fBnpm exec @usr/create\fR
29 \fBnpm init @usr@2.0.0\fR -> \fBnpm exec @usr/create@2.0.0\fR
31 \fBnpm init @usr/foo@2.0.0\fR -> \fBnpm exec @usr/create-foo@2.0.0\fR
[all …]
|
| /third_party/node/deps/npm/docs/content/using-npm/ |
| D | scripts.md | 4 description: How npm handles the "scripts" field
12 `npm run-script <stage>` or `npm run <stage>` for short. *Pre* and *post*
15 `npm explore <pkg> -- npm run <stage>`.
33 In this example `npm run compress` would execute these scripts as
44 **prepare** (since `npm@4.0.0`)
45 * Runs BEFORE the package is packed, i.e. during `npm publish`
46 and `npm pack`
47 * Runs on local `npm install` without any arguments
55 * As of `npm@7` these scripts run in the background.
59 * Does not run during `npm publish`, but does run during `npm ci`
[all …]
|
| D | scope.md | 9 All npm packages have a name. Some package names also have a scope. A scope
19 things about the way npm treats the package.
21 Each npm user/organization has their own scope, and only you can add packages
26 Scoped packages can be published and installed as of `npm@2` and are supported
27 by the primary npm registry. Unscoped packages can depend on scoped packages and
28 vice versa. The npm client is backwards-compatible with unscoped registries,
40 `@` symbol, in `npm install`:
43 npm install @myorg/mypackage
54 Note that if the `@` symbol is omitted, in either case, npm will instead attempt to
55 install from GitHub; see [`npm install`](/commands/npm-install).
[all …]
|
| /third_party/node/deps/npm/tap-snapshots/test/lib/commands/ |
| D | publish.js.test.cjs | 13 + @npm/test-package@1.0.0
146 + @npm/test-package@1.0.0
150 + @npm/test-package@1.0.0
190 "_id": "npm@{VERSION}",
195 "npm": "bin/npm-cli.js",
199 "url": "https://github.com/npm/cli/issues",
233 "man/man1/npm-access.1",
234 "man/man1/npm-adduser.1",
235 "man/man1/npm-audit.1",
236 "man/man1/npm-bugs.1",
[all …]
|
| /third_party/node/deps/npm/man/man7/ |
| D | scripts.7 | 3 \fBscripts\fR - How npm handles the "scripts" field
6 …npm run-script <stage>\fR or \fBnpm run <stage>\fR for short. \fIPre\fR and \fIpost\fR commands wi…
23 In this example \fBnpm run compress\fR would execute these scripts as described.
33 \fBprepare\fR (since \fBnpm@4.0.0\fR)
36 Runs BEFORE the package is packed, i.e. during \fBnpm publish\fR and \fBnpm pack\fR
38 Runs on local \fBnpm install\fR without any arguments
44 As of \fBnpm@7\fR these scripts run in the background. To see the output, run with: \fB--foreground…
51 Does not run during \fBnpm publish\fR, but does run during \fBnpm ci\fR and \fBnpm install\fR. See …
58 Runs BEFORE the package is prepared and packed, ONLY on \fBnpm publish\fR.
65 Runs BEFORE a tarball is packed (on "\fBnpm pack\fR", "\fBnpm publish\fR", and when installing a gi…
[all …]
|
| /third_party/typescript/tests/baselines/reference/ |
| D | moduleExportAssignment2.symbols | 1 === tests/cases/conformance/salsa/npm.js ===
2 var npm = module.exports = function (tree) {
3 >npm : Symbol(npm, Decl(npm.js, 0, 3))
4 >module.exports : Symbol(module.exports, Decl(npm.js, 0, 0))
5 >module : Symbol(npm, Decl(npm.js, 0, 9))
6 >exports : Symbol(npm, Decl(npm.js, 0, 9))
7 >tree : Symbol(tree, Decl(npm.js, 0, 37))
10 >module.exports.asReadInstalled : Symbol(asReadInstalled, Decl(npm.js, 1, 1))
11 >module.exports : Symbol(asReadInstalled, Decl(npm.js, 1, 1))
12 >module : Symbol(module, Decl(npm.js, 0, 9), Decl(npm.js, 3, 13))
[all …]
|
| /third_party/node/deps/npm/tap-snapshots/test/lib/utils/ |
| D | update-notifier.js.test.cjs | 10 New [31mmajor[39m version of npm available! [31m122.420.69[39m -> [32m123.420.69[39m
11 Changelog: [36mhttps://github.com/npm/cli/releases/tag/v123.420.69[39m
12 Run [32mnpm install -g npm@123.420.69[39m to update!
18 New major version of npm available! 122.420.69 -> 123.420.69
19 Changelog: <https://github.com/npm/cli/releases/tag/v123.420.69>
20 Run \`npm install -g npm@123.420.69\` to update!
26 New [33mminor[39m version of npm available! [31m123.419.69[39m -> [32m123.420.69[39m
27 Changelog: [36mhttps://github.com/npm/cli/releases/tag/v123.420.69[39m
28 Run [32mnpm install -g npm@123.420.69[39m to update!
34 New minor version of npm available! 123.419.69 -> 123.420.69
[all …]
|
| /third_party/node/deps/npm/ |
| D | README.md | 1 # npm - a JavaScript package manager
3 [](https://npm.im/npm)
4 [](https://npm.im/npm)
5 [](https://github.com/npm…
6 [](https://…
10 …ollowing versions of [Node.js](https://nodejs.org/en/download/) must be installed to run **`npm`**:
17 **`npm`** comes bundled with [**`node`**](https://nodejs.org/), & most third-party distributions, b…
21 You can download & install **`npm`** directly from [**npmjs**.com](https://npmjs.com/) using our cu…
29 If you're looking to manage multiple versions of **`Node.js`** &/or **`npm`**, consider using a [no…
34 npm <command>
[all …]
|