@pnpm/installing.commands 1100.10.2 → 1100.10.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/lib/runPacquet.js +11 -8
  2. package/package.json +36 -36
package/lib/runPacquet.js CHANGED
@@ -198,16 +198,19 @@ function pacquetSupportsResolution(version) {
198
198
  * surface pnpm itself accepts on `install`, so the flags don't need
199
199
  * reshaping.
200
200
  *
201
- * Flags we always inject ourselves (`--frozen-lockfile`,
201
+ * Flags we manage ourselves (`--frozen-lockfile`,
202
202
  * `--ignore-manifest-check`) are dropped in every form the user can
203
203
  * type them — positive (`--frozen-lockfile`), negated
204
- * (`--no-frozen-lockfile`), and any `=value` form. Pacquet's clap
205
- * defines these as plain `#[clap(long)] bool` flags, so a duplicate
206
- * `--frozen-lockfile` or a conflicting `--no-frozen-lockfile`
207
- * crashes the parser with "used multiple times" / "unexpected
208
- * argument". The user's `--no-frozen-lockfile` intent is already
209
- * honored upstream (pnpm did a fresh resolve before delegating);
210
- * pacquet's role here is just lockfile-driven materialization.
204
+ * (`--no-frozen-lockfile`), and any `=value` form. pnpm resolves the
205
+ * frozen-lockfile setting itself and encodes the decision in the mode
206
+ * it hands pacquet: a resolving install (pacquet resolves and writes
207
+ * the lockfile, no `--frozen-lockfile` injected) or a frozen
208
+ * materialization (pacquet is pinned to the lockfile via an injected
209
+ * `--frozen-lockfile`) — see `frozenArgs` in `makeRun`. Forwarding the
210
+ * user's own token would contradict that choice: pacquet accepts a
211
+ * `--no-<flag>` negation for every boolean flag with last-one-wins
212
+ * override semantics, so a user `--no-frozen-lockfile` sitting next to
213
+ * our injected `--frozen-lockfile` would flip the pinning back off.
211
214
  *
212
215
  * `--reporter` is stripped in any form (`--reporter=foo`,
213
216
  * `--reporter foo`): pacquet's `reporter` is a clap value option
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pnpm/installing.commands",
3
- "version": "1100.10.2",
3
+ "version": "1100.10.3",
4
4
  "description": "Commands for installation",
5
5
  "keywords": [
6
6
  "pnpm",
@@ -47,54 +47,54 @@
47
47
  "ramda": "npm:@pnpm/ramda@0.28.1",
48
48
  "render-help": "^2.0.0",
49
49
  "version-selector-type": "^3.0.0",
50
- "@pnpm/building.policy": "1100.0.11",
51
- "@pnpm/catalogs.config": "1100.0.2",
52
- "@pnpm/cli.command": "1100.0.1",
53
- "@pnpm/building.after-install": "1102.0.3",
54
50
  "@pnpm/catalogs.types": "1100.0.0",
55
- "@pnpm/cli.utils": "1101.0.13",
51
+ "@pnpm/catalogs.config": "1100.0.2",
52
+ "@pnpm/building.policy": "1100.0.12",
53
+ "@pnpm/building.after-install": "1102.0.4",
56
54
  "@pnpm/cli.common-cli-options-help": "1100.0.2",
57
55
  "@pnpm/config.matcher": "1100.0.1",
58
56
  "@pnpm/config.pick-registry-for-package": "1100.0.9",
59
- "@pnpm/config.reader": "1101.11.0",
57
+ "@pnpm/config.reader": "1101.11.1",
58
+ "@pnpm/config.version-policy": "1100.1.6",
60
59
  "@pnpm/config.writer": "1100.0.15",
60
+ "@pnpm/cli.utils": "1101.0.13",
61
61
  "@pnpm/constants": "1100.0.0",
62
- "@pnpm/deps.security.signatures": "1101.2.3",
63
- "@pnpm/config.version-policy": "1100.1.6",
64
62
  "@pnpm/deps.path": "1100.0.8",
65
- "@pnpm/error": "1100.0.1",
66
- "@pnpm/fs.read-modules-dir": "1100.0.1",
67
- "@pnpm/deps.status": "1100.1.4",
68
- "@pnpm/deps.inspection.outdated": "1100.1.11",
63
+ "@pnpm/deps.security.signatures": "1101.2.3",
64
+ "@pnpm/deps.inspection.outdated": "1100.1.12",
69
65
  "@pnpm/fs.graceful-fs": "1100.1.0",
66
+ "@pnpm/fs.read-modules-dir": "1100.0.1",
67
+ "@pnpm/global.commands": "1100.0.32",
70
68
  "@pnpm/hooks.pnpmfile": "1100.0.17",
71
- "@pnpm/global.commands": "1100.0.31",
69
+ "@pnpm/installing.context": "1100.0.22",
72
70
  "@pnpm/installing.dedupe.check": "1100.1.2",
71
+ "@pnpm/deps.status": "1100.1.5",
72
+ "@pnpm/installing.deps-installer": "1102.2.1",
73
+ "@pnpm/installing.env-installer": "1102.0.4",
74
+ "@pnpm/lockfile.fs": "1100.1.9",
73
75
  "@pnpm/installing.dedupe.issues-renderer": "1100.0.1",
74
- "@pnpm/installing.context": "1100.0.21",
75
- "@pnpm/installing.deps-installer": "1102.2.0",
76
- "@pnpm/lockfile.fs": "1100.1.8",
77
76
  "@pnpm/network.auth-header": "1101.1.3",
78
- "@pnpm/installing.env-installer": "1102.0.3",
79
77
  "@pnpm/network.fetch": "1100.1.4",
80
- "@pnpm/lockfile.types": "1100.0.13",
78
+ "@pnpm/resolving.parse-wanted-dependency": "1100.0.1",
81
79
  "@pnpm/pkg-manifest.reader": "1100.0.9",
82
80
  "@pnpm/pkg-manifest.utils": "1100.2.6",
83
- "@pnpm/resolving.parse-wanted-dependency": "1100.0.1",
84
- "@pnpm/store.connection-manager": "1100.3.3",
85
- "@pnpm/resolving.npm-resolver": "1102.1.1",
86
- "@pnpm/resolving.resolver-base": "1100.5.1",
81
+ "@pnpm/store.connection-manager": "1100.3.4",
87
82
  "@pnpm/store.controller": "1102.0.3",
88
- "@pnpm/types": "1101.3.2",
83
+ "@pnpm/lockfile.types": "1100.0.13",
89
84
  "@pnpm/workspace.project-manifest-reader": "1100.0.14",
90
85
  "@pnpm/workspace.project-manifest-writer": "1100.0.8",
91
- "@pnpm/workspace.projects-filter": "1100.0.24",
92
- "@pnpm/workspace.projects-graph": "1100.0.21",
93
- "@pnpm/workspace.projects-reader": "1101.0.13",
94
- "@pnpm/workspace.root-finder": "1100.0.3",
86
+ "@pnpm/workspace.projects-filter": "1100.0.25",
87
+ "@pnpm/resolving.resolver-base": "1100.5.1",
95
88
  "@pnpm/workspace.projects-sorter": "1100.0.8",
96
- "@pnpm/workspace.state": "1100.0.25",
97
- "@pnpm/workspace.workspace-manifest-writer": "1100.0.15"
89
+ "@pnpm/resolving.npm-resolver": "1102.1.2",
90
+ "@pnpm/workspace.root-finder": "1100.0.3",
91
+ "@pnpm/types": "1101.3.2",
92
+ "@pnpm/workspace.projects-reader": "1101.0.13",
93
+ "@pnpm/workspace.state": "1100.0.26",
94
+ "@pnpm/error": "1100.0.1",
95
+ "@pnpm/workspace.workspace-manifest-writer": "1100.0.15",
96
+ "@pnpm/cli.command": "1100.0.1",
97
+ "@pnpm/workspace.projects-graph": "1100.0.22"
98
98
  },
99
99
  "peerDependencies": {
100
100
  "@pnpm/logger": "^1100.0.0"
@@ -119,17 +119,17 @@
119
119
  "write-yaml-file": "^6.0.0",
120
120
  "@pnpm/assert-project": "1100.0.18",
121
121
  "@pnpm/logger": "1100.0.0",
122
- "@pnpm/installing.modules-yaml": "1100.0.9",
123
- "@pnpm/installing.commands": "1100.10.2",
124
122
  "@pnpm/store.index": "1100.2.1",
125
123
  "@pnpm/prepare": "1100.0.18",
126
- "@pnpm/test-fixtures": "1100.0.0",
124
+ "@pnpm/installing.commands": "1100.10.3",
127
125
  "@pnpm/testing.command-defaults": "1100.0.8",
128
- "@pnpm/testing.mock-agent": "1101.0.4",
129
- "@pnpm/testing.registry-mock": "1100.0.8",
130
126
  "@pnpm/test-ipc-server": "1100.0.0",
127
+ "@pnpm/test-fixtures": "1100.0.0",
128
+ "@pnpm/testing.mock-agent": "1101.0.4",
131
129
  "@pnpm/worker": "1100.2.3",
132
- "@pnpm/workspace.projects-filter": "1100.0.24"
130
+ "@pnpm/testing.registry-mock": "1100.0.8",
131
+ "@pnpm/workspace.projects-filter": "1100.0.25",
132
+ "@pnpm/installing.modules-yaml": "1100.0.9"
133
133
  },
134
134
  "engines": {
135
135
  "node": ">=22.13"