Home
last modified time | relevance | path

Searched full:npm (Results 1 – 25 of 2316) sorted by relevance

12345678910>>...93

/third_party/node/deps/npm/changelogs/
DCHANGELOG-2.md7 * [`cdd60e733`](https://github.com/npm/npm/commit/cdd60e733905a9994e1d6d832996bfdd12abeaee)
23 Note that `npm@4` will almost certainly be released next month! It's not final
26 `npm@2` will be reduced to essentially maintenance, so we can better focus on
27 `npm@3` as the new LTS version (which will go into `node@6`), and `npm@4` as our
32 * [`8f71038`](https://github.com/npm/npm/commit/8f71038310501ad5bc7445b2fa2ff0eaa377919a)
33 [#13892](https://github.com/npm/npm/pull/13892)
36 * [`e81b4f1`](https://github.com/npm/npm/commit/e81b4f1d18a4d79b7af8342747f2ed7dc3e84f0a)
37 [#12438](https://github.com/npm/npm/issues/12438)
41 * [`f89789f`](https://github.com/npm/npm/commit/f89789f43d65bfc74f64f15a99356841377e1af3)
42 [#13655](https://github.com/npm/npm/pull/13655)
[all …]
DCHANGELOG-5.md9 * [`3dcc240db`](https://github.com/npm/npm/commit/3dcc240dba5258532990534f1bd8a25d1698b0bf)
16 ### EXTENDED `npm init` SCAFFOLDING
19 lodash fame, `npm init` can now be used to invoke custom scaffolding tools!
21 You can now do things like `npm init react-app` or `npm init esm` to scaffold an
22 npm package by running `create-react-app` and `create-esm`, respectively. This
23 also adds an `npm create` alias, to correspond to Yarn's `yarn create` feature,
26 * [`adc009ed4`](https://github.com/npm/npm/commit/adc009ed4114ed1e692f8ef15123af6040615cee)
27 [`f363edd04`](https://github.com/npm/npm/commit/f363edd04f474fa64e4d97228c0b2a7858f21e7c)
28 [`f03b45fb2`](https://github.com/npm/npm/commit/f03b45fb217df066c3cb7715f9c0469d84e5aa8e)
29 [`13adcbb52`](https://github.com/npm/npm/commit/13adcbb527fb8214e5f2233706c6b72ce072f3fa)
[all …]
DCHANGELOG-3.md3 See the discussion on [#14042](https://github.com/npm/npm/issues/14042) for
7 to `npm@4`, which has everything in this release and more.
11 * [`9aebe98`](https://github.com/npm/npm/commit/9aebe982114ea2107f46baa1dcb11713b4aaad04)
12 [#14117](https://github.com/npm/npm/pull/14117)
23 released.) As a small team with limited resources, the npm CLI team is
27 * [`c82ecfd`](https://github.com/npm/npm/commit/c82ecfdbe0b5f318a175714a8753efe4dfd3e4b3)
28 [#14503](https://github.com/npm/npm/pull/14503)
40 This is ALSO the ULTIMATE release of `npm` version 3. That's right, in
42 `npm` will be hitting the big 4.0.
49 [4.x milestone](https://github.com/npm/npm/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.x),
[all …]
DCHANGELOG-4.md3 A little release to tide you over while we hammer out the last bits for npm@5.
7 * [`d13c9b2f2`](https://github.com/npm/npm/commit/d13c9b2f24b6380427f359b6e430b149ac8aaa79)
13 * [`f08c66323`](https://github.com/npm/npm/commit/f08c663231099f7036eb82b92770806a3a79cdf1)
14 [#16213](https://github.com/npm/npm/pull/16213)
15 Add `--allow-same-version` option to `npm version` so that you can use `npm version` to run
19 * [`f5e8becd0`](https://github.com/npm/npm/commit/f5e8becd05e0426379eb0c999abdbc8e87a7f6f2)
22 an `npm-debug.log` even on success and add an entry to `_timing.json` in your cache with
28 * [`9c860f2ed`](https://github.com/npm/npm/commit/9c860f2ed3bdea1417ed059b019371cd253db2ad)
29 [#16021](https://github.com/npm/npm/pull/16021)
30 Fix a crash in `npm doctor` when used with a registry that does not support
[all …]
DCHANGELOG-1.md5 In a special one-off release as part of the [strategy to get a version of npm
7 registry](https://github.com/nodejs/LTS/issues/37), modify npm to print out
8 this deprecation banner literally every time npm is invoked to do anything:
11 npm WARN deprecated This version of npm lacks support for important features,
12 npm WARN deprecated such as scoped packages, offered by the primary npm
13 npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
14 npm WARN deprecated latest stable version. To upgrade to npm@2, run:
15 npm WARN deprecated
16 npm WARN deprecated npm -g install npm@latest-2
17 npm WARN deprecated
[all …]
/third_party/node/deps/npm/docs/public/static/d/
D2215187023.json1 …npm-adduser"},"frontmatter":{"description":null,"section":null,"title":""}},{"fields":{"slug":"/cl…
/third_party/node/deps/npm/
DCHANGELOG.md4 * [`19108ca5b`](https://github.com/npm/cli/commit/19108ca5be1b3e7e9787dac3131aafe2722c6218)
7 * [`7a0574074`](https://github.com/npm/cli/commit/7a05740743ac9d9229e2dc9e1b9ca8b57d58c789)
15 * [`906d647e1`](https://github.com/npm/cli/commit/906d647e1cacd74243abcacba3bade80437f30f5)
23 * [`4a91e48aa`](https://github.com/npm/cli/commit/4a91e48aa92be5b2739ebcdd8a9a841ff5cb6817)
27 * [`ab80a7cf0`](https://github.com/npm/cli/commit/ab80a7cf092d52f4b055cc6d03c38b6115c4b582)
28 `npm-user-validate@1.0.1`
30 * [`6b2ab9d53`](https://github.com/npm/cli/commit/6b2ab9d532ef8ffce326f4caa23eb27f83765acd)
37 * [`9262e8c88`](https://github.com/npm/cli/commit/9262e8c88f2f828206423928b8e21eea67f4801a)
38 [#1575](https://github.com/npm/cli/pull/1575)
39 npm install --dev deprecation message
[all …]
DREADME.md1 npm(1) -- a JavaScript package manager
4 [![Build Status](https://img.shields.io/travis/npm/cli/latest.svg)](https://travis-ci.org/npm/cli)
10 Much more info will be available via `npm help` once it's installed.
16 To install an old **and unsupported** version of npm that works on node v5
19 **npm is configured to use npm, Inc.'s public registry at
20 <https://registry.npmjs.org> by default.** Use of the npm public registry
23 You can configure npm to use any compatible registry you
29 npm is bundled with [node](https://nodejs.org/en/download/).
33 [Get the MSI](https://nodejs.org/en/download/). npm is in it.
37 [Get the pkg](https://nodejs.org/en/download/). npm is in it.
[all …]
/third_party/node/deps/npm/test/fixtures/
Dgithub-com-BryanDonovan-dummy-npm-foo.git.tar.gz
Dgithub-com-BryanDonovan-dummy-npm-bar.git.tar.gz
Dgithub-com-BryanDonovan-dummy-npm-buzz.git.tar.gz
Dgithub-com-BryanDonovan-npm-git-test.git.tar.gz
/third_party/node/deps/npm/docs/content/cli-commands/
Dnpm-install.md3 title: npm-install
7 # npm-install(1)
14 npm install (with no args, in package dir)
15 npm install [<@scope>/]<name>
16 npm install [<@scope>/]<name>@<tag>
17 npm install [<@scope>/]<name>@<version>
18 npm install [<@scope>/]<name>@<version range>
19 npm install <alias>@npm:<name>
20 npm install <git-host>:<git-user>/<repo-name>
21 npm install <git repo url>
[all …]
Dnpm-doctor.md3 title: npm-doctor
7 # npm-doctor(1)
14 npm doctor
19 `npm doctor` runs a set of checks to ensure that your npm installation has
20 what it needs to manage your JavaScript packages. npm is mostly a standalone tool, but it does
23 + Node.js and git must be executable by npm.
24 + The primary npm registry, `registry.npmjs.com`, or another service that uses
26 + The directories that npm uses, `node_modules` (both locally and globally),
28 + The npm cache exists, and the package tarballs within it aren't corrupt.
30 Without all of these working properly, npm may not work properly. Many issues
[all …]
Dnpm-cache.md3 title: npm-cache
7 # npm-cache(1)
14 npm cache add <tarball file>
15 npm cache add <folder>
16 npm cache add <tarball url>
17 npm cache add <name>@<version>
19 npm cache clean [<path>]
20 aliases: npm cache clear, npm cache rm
22 npm cache verify
27 Used to add, list, or clean the npm cache folder.
[all …]
/third_party/node/deps/npm/node_modules/npm-pick-manifest/
DCHANGELOG.md6 ## [3.0.2](https://github.com/npm/npm-pick-manifest/compare/v3.0.1...v3.0.2) (2019-08-30)
11 ## [3.0.1](https://github.com/npm/npm-pick-manifest/compare/v3.0.0...v3.0.1) (2019-08-28)
16 …rsions ([003286e](https://github.com/npm/npm-pick-manifest/commit/003286e)), closes [#2](https://g…
21 # [3.0.0](https://github.com/npm/npm-pick-manifest/compare/v2.2.3...v3.0.0) (2019-08-20)
26 …policy ([ad2a962](https://github.com/npm/npm-pick-manifest/commit/ad2a962)), closes [#1](https://g…
34 PR-URL: https://github.com/npm/npm-pick-manifest/pull/1
40 ## [2.2.3](https://github.com/npm/npm-pick-manifest/compare/v2.2.2...v2.2.3) (2018-10-31)
45 * **enjoyBy:** rework semantics for enjoyBy again ([5e89b62](https://github.com/npm/npm-pick-manife…
50 ## [2.2.2](https://github.com/npm/npm-pick-manifest/compare/v2.2.1...v2.2.2) (2018-10-31)
55 * **enjoyBy:** rework semantics for enjoyBy ([5684f45](https://github.com/npm/npm-pick-manifest/com…
[all …]
DREADME.md1 …npm-pick-manifest [![npm version](https://img.shields.io/npm/v/npm-pick-manifest.svg)](https://npm…
3 [`npm-pick-manifest`](https://github.com/npm/npm-pick-manifest) is a standalone
4 implementation of [npm](https://npmjs.com)'s semver range resolution algorithm.
8 `$ npm install --save npm-pick-manifest`
21 const pickManifest = require('npm-pick-manifest')
23 fetch('https://registry.npmjs.org/npm-pick-manifest').then(res => {
27 }) // get same manifest as npm would get if you `npm i npm-pick-manifest@^1.0.0`
32 * Uses npm's exact semver resolution algorithm
37 The npm-pick-manifest team enthusiastically welcomes contributions and project participation!
49 Packuments are anything returned by metadata URLs from the npm registry. That
[all …]
/third_party/flutter/skia/modules/pathkit/
DMakefile4 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/node_modules/npm-audit-report/
DCHANGELOG.md6 ## [1.3.3](https://github.com/npm/npm-audit-report/compare/v1.3.2...v1.3.3) (2020-03-26)
11 ## [1.3.2](https://github.com/npm/npm-audit-report/compare/v1.3.1...v1.3.2) (2018-12-18)
16 …install action ([#28](https://github.com/npm/npm-audit-report/issues/28)) ([5e27893](https://githu…
17 * **security:** audit fix ([ff9faf3](https://github.com/npm/npm-audit-report/commit/ff9faf3))
18 …audit response ([#34](https://github.com/npm/npm-audit-report/issues/34)) ([e2fe95b](https://githu…
23 ## [1.3.1](https://github.com/npm/npm-audit-report/compare/v1.3.0...v1.3.1) (2018-07-10)
28 # [1.3.0](https://github.com/npm/npm-audit-report/compare/v1.2.1...v1.3.0) (2018-07-09)
33 * **deps:** remove object.values dependency ([2c5374a](https://github.com/npm/npm-audit-report/comm…
34 …level severity ([#18](https://github.com/npm/npm-audit-report/issues/18)) ([807db5a](https://githu…
35 …in other tests ([#23](https://github.com/npm/npm-audit-report/issues/23)) ([a94449f](https://githu…
[all …]
/third_party/node/deps/npm/man/man1/
Dnpm-doctor.11 .TH "NPM\-DOCTOR" "1" "February 2021" "" ""
3 \fBnpm-doctor\fR \- Check your environments
13 \fBnpm doctor\fP runs a set of checks to ensure that your npm installation has
14 what it needs to manage your JavaScript packages\. npm is mostly a standalone tool, but it does
18 Node\.js and git must be executable by npm\.
20 The primary npm registry, \fBregistry\.npmjs\.com\fP, or another service that uses
23 The directories that npm uses, \fBnode_modules\fP (both locally and globally),
26 The npm cache exists, and the package tarballs within it aren't corrupt\.
30 Without all of these working properly, npm may not work properly\. Many issues
31 are often attributable to things that are outside npm's code base, so \fBnpm
[all …]
Dnpm-install.11 .TH "NPM\-INSTALL" "1" "February 2021" "" ""
3 \fBnpm-install\fR \- Install a package
13 npm install <alias>@npm:<name>
20 aliases: npm i, npm add
28 will be driven by that, with an \fBnpm\-shrinkwrap\.json\fP taking precedence if both
29 files exist\. See npm help package\-lock\.json and npm help \fBshrinkwrap\fP\|\.
34 a) a folder containing a program described by a npm help \fBpackage\.json\fP file
40 d) a \fB<name>@<version>\fP that is published on the registry (see npm help \fBregistry\fP) with (c)
42 e) a \fB<name>@<tag>\fP (see npm help \fBdist\-tag\fP) that points to (d)
51 benefits of using npm if you just want to write a node program (a), and
[all …]
/third_party/node/deps/npm/bin/
Dnpm-cli.js3 // windows: running "npm blah" in this folder will invoke WSH, not node.
7 'npm does not work when run\n' +
10 "or type 'npm.cmd <args>',\n" +
11 "or type 'node npm <args>'."
17 process.title = 'npm'
28 var npm = require('../lib/npm.js')
38 // if npm is called as "npmg" or "npm_g", then
41 process.argv.splice(1, 1, 'npm', '-g')
48 npm.argv = conf.argv.remain
49 if (npm.deref(npm.argv[0])) npm.command = npm.argv.shift()
[all …]
/third_party/node/deps/npm/node_modules/libcipm/
DCHANGELOG.md6 ## [4.0.8](https://github.com/npm/libcipm/compare/v4.0.7...v4.0.8) (2020-03-25)
11 * add repo to bin pkg, bump to 2.0.1 ([ed2d735](https://github.com/npm/libcipm/commit/ed2d735))
16 ## [4.0.7](https://github.com/npm/libcipm/compare/v4.0.4...v4.0.7) (2019-10-09)
21 …he dir itself ([f668181](https://github.com/npm/libcipm/commit/f668181)), closes [#3](https://gith…
24 ## [4.0.4](https://github.com/npm/libcipm/compare/v4.0.3...v4.0.4) (2019-09-24)
29 …ries properly ([576ab36](https://github.com/npm/libcipm/commit/576ab36)), closes [#4](https://gith…
34 ## [4.0.3](https://github.com/npm/libcipm/compare/v4.0.2...v4.0.3) (2019-08-12)
39 * do not pass opts.log to lifecycle ([46b2101](https://github.com/npm/libcipm/commit/46b2101))
44 ## [4.0.2](https://github.com/npm/libcipm/compare/v4.0.1...v4.0.2) (2019-08-12)
49 ## [4.0.1](https://github.com/npm/libcipm/compare/v4.0.0...v4.0.1) (2019-08-12)
[all …]
/third_party/node/deps/npm/docs/content/using-npm/
Dscope.md2 section: using-npm
12 All npm packages have a name. Some package names also have a scope. A scope
22 things about the way npm treats the package.
24 Each npm user/organization has their own scope, and only you can add packages
29 Scoped packages can be published and installed as of `npm@2` and are supported
30 by the primary npm registry. Unscoped packages can depend on scoped packages and
31 vice versa. The npm client is backwards-compatible with unscoped registries,
43 `@` symbol, in `npm install`:
46 npm install @myorg/mypackage
57 Note that if the `@` symbol is omitted, in either case, npm will instead attempt to
[all …]
/third_party/node/deps/npm/node_modules/libnpx/
DCHANGELOG.md6 ## [10.2.4](https://github.com/npm/npx/compare/v10.2.3...v10.2.4) (2020-07-20)
11 ## [10.2.3](https://github.com/npm/npx/compare/v10.2.2...v10.2.3) (2020-03-24)
16 ## [10.2.2](https://github.com/npm/npx/compare/v10.2.1...v10.2.2) (2020-01-28)
21 * correct Kat's github url ([9a23db1](https://github.com/npm/npx/commit/9a23db1))
22 * install latest npm on travis for node 6 ([e0eb3cb](https://github.com/npm/npx/commit/e0eb3cb))
23 * Update changelog to fix old issue links ([3733137](https://github.com/npm/npx/commit/3733137))
28 # [10.2.0](https://github.com/npm/npx/compare/v10.1.1...v10.2.0) (2018-04-13)
33 …63](https://github.com/zkat/npx/issues/163)) ([11d9fe0](https://github.com/npm/npx/commit/11d9fe0))
34 …74](https://github.com/zkat/npx/issues/174)) ([cba97bb](https://github.com/npm/npx/commit/cba97bb))
35 …73](https://github.com/zkat/npx/issues/173)) ([fe0d48a](https://github.com/npm/npx/commit/fe0d48a)…
[all …]

12345678910>>...93