Loading workspace insights... Statistics interval
7 days30 daysLatest CI Pipeline Executions
fd383494 CLI: skip redundant registry probes during sandbox creation
Sandbox creation spawned ~24 package-manager subprocesses just to resolve
versions, measured via a timestamped local reproduction of angular-vite
sandbox creation and confirmed in the CI create-job logs:
- latestVersion() probed the registry for every storybook package even
though the CLI ships the authoritative version map (versions.ts) and the
sandbox registry (verdaccio) serves exactly those versions. Inside
sandbox creation (IN_STORYBOOK_SANDBOX, set by the monorepo task runner
and never by real user installs) the probe is now short-circuited to the
versions map. On CI the resulting specifiers are byte-identical; in
link-mode local sandboxes storybook packages get ^version instead of an
exact pin, where the linked workspace overrides resolution anyway.
- addDependencies(skipInstall) resolved a version for every dependency
serially - including dependencies whose specifier already carried one,
discarding the result. Lookups now only happen for unversioned specifiers
and run concurrently, with insertion order kept deterministic. This also
speeds up real 'storybook init' runs.
- getInstalledVersion() spawned a full dependency-graph walk per package
(yarn info --recursive), which exits 1 with usage output for packages
that are not installed at all - addon-vitest probes vitest, msw and
coverage packages this way on every sandbox. The module's own
package.json is now resolved first (a plain fs read, PnP included), and
the graph walk only runs as a fallback for declared dependencies that
don't resolve directly (e.g. pnpm virtual store layouts).
- The 'sb repro' command probed npm for latest/next before downloading the
template; inside sandbox creation those two roundtrips only feed the
'you are behind' warning copy and are skipped.
The proxy unit tests asserting registry-probe behavior now stub
IN_STORYBOOK_SANDBOX off explicitly - the repo-level .env marks all vitest
runs as sandbox context - and a new test pins the short-circuit contract.
Measured locally (angular-vite, full creation): 24 -> 8 version-probe
spawns; 56s -> 48s on top of the CI-side trims, 107s cumulative baseline. fd383494 CLI: skip redundant registry probes during sandbox creation
Sandbox creation spawned ~24 package-manager subprocesses just to resolve
versions, measured via a timestamped local reproduction of angular-vite
sandbox creation and confirmed in the CI create-job logs:
- latestVersion() probed the registry for every storybook package even
though the CLI ships the authoritative version map (versions.ts) and the
sandbox registry (verdaccio) serves exactly those versions. Inside
sandbox creation (IN_STORYBOOK_SANDBOX, set by the monorepo task runner
and never by real user installs) the probe is now short-circuited to the
versions map. On CI the resulting specifiers are byte-identical; in
link-mode local sandboxes storybook packages get ^version instead of an
exact pin, where the linked workspace overrides resolution anyway.
- addDependencies(skipInstall) resolved a version for every dependency
serially - including dependencies whose specifier already carried one,
discarding the result. Lookups now only happen for unversioned specifiers
and run concurrently, with insertion order kept deterministic. This also
speeds up real 'storybook init' runs.
- getInstalledVersion() spawned a full dependency-graph walk per package
(yarn info --recursive), which exits 1 with usage output for packages
that are not installed at all - addon-vitest probes vitest, msw and
coverage packages this way on every sandbox. The module's own
package.json is now resolved first (a plain fs read, PnP included), and
the graph walk only runs as a fallback for declared dependencies that
don't resolve directly (e.g. pnpm virtual store layouts).
- The 'sb repro' command probed npm for latest/next before downloading the
template; inside sandbox creation those two roundtrips only feed the
'you are behind' warning copy and are skipped.
The proxy unit tests asserting registry-probe behavior now stub
IN_STORYBOOK_SANDBOX off explicitly - the repo-level .env marks all vitest
runs as sandbox context - and a new test pins the short-circuit contract.
Measured locally (angular-vite, full creation): 24 -> 8 version-probe
spawns; 56s -> 48s on top of the CI-side trims, 107s cumulative baseline. fd383494 CLI: skip redundant registry probes during sandbox creation
Sandbox creation spawned ~24 package-manager subprocesses just to resolve
versions, measured via a timestamped local reproduction of angular-vite
sandbox creation and confirmed in the CI create-job logs:
- latestVersion() probed the registry for every storybook package even
though the CLI ships the authoritative version map (versions.ts) and the
sandbox registry (verdaccio) serves exactly those versions. Inside
sandbox creation (IN_STORYBOOK_SANDBOX, set by the monorepo task runner
and never by real user installs) the probe is now short-circuited to the
versions map. On CI the resulting specifiers are byte-identical; in
link-mode local sandboxes storybook packages get ^version instead of an
exact pin, where the linked workspace overrides resolution anyway.
- addDependencies(skipInstall) resolved a version for every dependency
serially - including dependencies whose specifier already carried one,
discarding the result. Lookups now only happen for unversioned specifiers
and run concurrently, with insertion order kept deterministic. This also
speeds up real 'storybook init' runs.
- getInstalledVersion() spawned a full dependency-graph walk per package
(yarn info --recursive), which exits 1 with usage output for packages
that are not installed at all - addon-vitest probes vitest, msw and
coverage packages this way on every sandbox. The module's own
package.json is now resolved first (a plain fs read, PnP included), and
the graph walk only runs as a fallback for declared dependencies that
don't resolve directly (e.g. pnpm virtual store layouts).
- The 'sb repro' command probed npm for latest/next before downloading the
template; inside sandbox creation those two roundtrips only feed the
'you are behind' warning copy and are skipped.
The proxy unit tests asserting registry-probe behavior now stub
IN_STORYBOOK_SANDBOX off explicitly - the repo-level .env marks all vitest
runs as sandbox context - and a new test pins the short-circuit contract.
Measured locally (angular-vite, full creation): 24 -> 8 version-probe
spawns; 56s -> 48s on top of the CI-side trims, 107s cumulative baseline.