| /third_party/node/deps/npm/test/lib/commands/ |
| D | ls.js | 620 peerDependencies: { property
652 peerDependencies: { property
725 peerDependencies: { property
756 peerDependencies: { property
789 peerDependencies: { property
837 peerDependencies: { property
935 peerDependencies: { property
969 peerDependencies: { property
2037 peerDependencies: { property
2069 peerDependencies: { property
[all …]
|
| D | query.js | 26 peerDependencies: { property
|
| /third_party/typescript/src/testRunner/unittests/tsserver/ |
| D | packageJsonInfo.ts | 10 peerDependencies: {
37 assert.ok(packageJsonInfo.peerDependencies);
82 assert.ok(packageJsonInfo2.peerDependencies);
99 assert.ok(packageJsonInfo2.peerDependencies);
|
| /third_party/node/deps/npm/node_modules/@npmcli/package-json/lib/ |
| D | update-dependencies.js | 56 const { dependencies: origProd, peerDependencies: origPeer } =
58 const { peerDependencies: newPeer } = result
|
| /third_party/node/deps/npm/node_modules/@npmcli/arborist/lib/ |
| D | edge.js | 198 if (pkg.peerDependencies?.[ref]) {
199 return pkg.peerDependencies[ref]
|
| D | node.js | 857 const pd = this.package.peerDependencies
861 const peerDependencies = {}
867 peerDependencies[name] = dep
870 this.#loadDepType(peerDependencies, 'peer', ad)
|
| D | add-rm-pkg-deps.js | 59 pkg.devDependencies[name] = pkg.peerDependencies[name]
|
| D | audit-report.js | 399 ...(tree.package.peerDependencies || {}),
|
| /third_party/node/deps/npm/node_modules/@npmcli/metavuln-calculator/lib/ |
| D | get-dep-spec.js | 8 peerDependencies: peerDeps = {},
|
| /third_party/typescript/src/jsTyping/ |
| D | jsTyping.ts | 16 peerDependencies?: MapLike<string>; property
229 …, manifest.devDependencies, manifest.optionalDependencies, manifest.peerDependencies], getOwnKeys);
|
| /third_party/node/deps/npm/docs/content/commands/ |
| D | npm-find-dupes.md | 66 conflicting `peerDependencies` will be treated as an install failure, even
70 By default, conflicting `peerDependencies` deep in the dependency graph will
73 the range set in their package's `peerDependencies` object.
|
| D | npm-install-ci-test.md | 101 conflicting `peerDependencies` will be treated as an install failure, even
105 By default, conflicting `peerDependencies` deep in the dependency graph will
108 the range set in their package's `peerDependencies` object.
|
| D | npm-ci.md | 155 conflicting `peerDependencies` will be treated as an install failure, even
159 By default, conflicting `peerDependencies` deep in the dependency graph will
162 the range set in their package's `peerDependencies` object.
|
| D | npm-dedupe.md | 126 conflicting `peerDependencies` will be treated as an install failure, even
130 By default, conflicting `peerDependencies` deep in the dependency graph will
133 the range set in their package's `peerDependencies` object.
|
| D | npm-install-test.md | 142 conflicting `peerDependencies` will be treated as an install failure, even
146 By default, conflicting `peerDependencies` deep in the dependency graph will
149 the range set in their package's `peerDependencies` object.
|
| D | npm-update.md | 269 conflicting `peerDependencies` will be treated as an install failure, even
273 By default, conflicting `peerDependencies` deep in the dependency graph will
276 the range set in their package's `peerDependencies` object.
|
| D | npm-link.md | 199 conflicting `peerDependencies` will be treated as an install failure, even
203 By default, conflicting `peerDependencies` deep in the dependency graph will
206 the range set in their package's `peerDependencies` object.
|
| D | npm-ls.md | 59 With the advent of automatic installation of `peerDependencies` in npm v7,
60 this gets even more curious, as `peerDependencies` are logically
|
| /third_party/node/deps/npm/tap-snapshots/test/lib/commands/ |
| D | outdated.js.test.cjs | 37 "type": "peerDependencies"
90 chai 1.0.0 1.0.1 1.0.1 node_modules/chai prefix peerDependencies
119 {CWD}/prefix/node_modules/chai:chai@1.0.1:chai@1.0.0:chai@1.0.1:prefix:peerDependencies:
|
| /third_party/node/deps/npm/test/lib/utils/completion/ |
| D | installed-deep.js | 17 peerDependencies: { property
|
| /third_party/node/deps/npm/node_modules/@npmcli/arborist/lib/arborist/ |
| D | reify.js | 1321 …g, 'peerDependencies', name) && (isLocalDep || !intersects(newSpec, pkg.peerDependencies[name]))) {
1322 pkg.peerDependencies[name] = newSpec
1330 pkg.peerDependencies[name] = newSpec
1428 peerDependencies = {},
1440 peerDependencies, property
|
| D | load-virtual.js | 129 const peer = lock.peerDependencies || {}
|
| /third_party/node/deps/npm/lib/commands/ |
| D | ls.js | 379 item.peerDependencies = node.package.peerDependencies || {}
|
| /third_party/node/deps/npm/docs/content/using-npm/ |
| D | config.md | 583 * Allow conflicting peerDependencies to be installed in the root project.
866 Causes npm to completely ignore `peerDependencies` when building a package
869 If a package cannot be installed because of overly strict `peerDependencies`
873 `peerDependencies` on disk, but will still design a tree such that
874 `peerDependencies` _could_ be unpacked in a correct place.
877 `peerDependencies` contract that meta-dependencies may rely on.
1324 Ignored if `--save-peer` is set, since peerDependencies cannot be bundled.
1361 Save installed packages to a package.json file as `peerDependencies`
1535 conflicting `peerDependencies` will be treated as an install failure, even
1539 By default, conflicting `peerDependencies` deep in the dependency graph will
[all …]
|
| /third_party/node/deps/npm/node_modules/@npmcli/arborist/ |
| D | README.md | 91 // - peer: save in peerDependencies, and remove any optional flag from
93 // - peerOptional: save in peerDependencies, and add a
145 `'peer'` for peerDependencies, `'dev'` for devDependencies, and
|