Zoltan Kochan 58429f9ba0 fix: resolve config dependencies from pnpm-workspace.yaml during install (#10969) ...

Previously, config dependencies could only be installed via `pnpm add --config`.
If a user manually added config deps to pnpm-workspace.yaml or deleted
pnpm-lock.env.yaml, `pnpm install` would fail because the resolution step
(fetching integrity from the registry) was missing.

Add `resolveAndInstallConfigDeps` which checks the env lockfile for missing
entries and resolves them from the npm registry before installing. This enables
two new workflows:
1. Manually adding config deps to pnpm-workspace.yaml
2. Deleting pnpm-lock.env.yaml and having `pnpm install` recreate it

2026-03-15 12:31:37 +01:00

..

cli-meta

feat: replace pkg with Node.js SEA for standalone executables (#10661)

2026-02-22 12:45:50 +01:00

cli-utils

fix: resolve config dependencies from pnpm-workspace.yaml during install (#10969)

2026-03-15 12:31:37 +01:00

command

build: enable @typescript-eslint/no-import-type-side-effects (#10630)

2026-03-08 00:02:48 +01:00

common-cli-options-help

feat(cli): add -F short alias for --filter (#10821)

2026-03-01 15:51:34 +01:00

default-reporter

style: enforce node: protocol for builtin imports (#10951)

2026-03-13 07:59:51 +01:00

parse-cli-args

style: enforce node: protocol for builtin imports (#10951)

2026-03-13 07:59:51 +01:00