Walkthrough

This PR introduces test sharding for the @pnpm/installing.deps-installer package. A constant shard count is defined in the meta-updater, the package-specific script generation logic is updated to compose a .test script from five sequential shard runs, and a new .test:shard entry point executes Jest with the same environment setup as before.

Changes

Test sharding for deps-installer

🎯 2 (Simple) | ⏱️ ~10 minutes

A sharded test path unfolds,
Five Jest runners in parallel bands—
Meta-updater's logic now molds,
Deps-installer's test stand expands.
🐰✨

• X
• Mastodon
• Reddit
• LinkedIn

Description

@pnpm/installing.deps-installer now runs Jest 5 times via shards, and each run’s with-registry
globalSetup creates a new temp registry storage directory that globalTeardown does not remove.
This increases leftover temporary storage from 1→5 directories per test invocation, which can
unnecessarily bloat disk usage on CI/local runs.

Code

installing/deps-installer/package.json[56]

+    ".test": "pn .test:shard --shard=1/5 && pn .test:shard --shard=2/5 && pn .test:shard --shard=3/5 && pn .test:shard --shard=4/5 && pn .test:shard --shard=5/5",

Evidence

The new .test script runs 5 Jest processes; the with-registry preset’s globalSetup creates a
unique temp storage dir per run and exposes it via PNPM_REGISTRY_MOCK_STORAGE, while
globalTeardown only kills the server and performs no directory cleanup, so the number of leftover
temp dirs increases with the shard count.

installing/deps-installer/package.json[49-58]
utils/jest-config/with-registry/globalSetup.js[16-29]
utils/jest-config/with-registry/globalTeardown.js[1-3]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Sharding runs Jest 5 separate times. The with-registry Jest preset creates a new temp storage directory in `globalSetup` (`mkdtempSync(...)`) but `globalTeardown` currently only kills the server and does not delete the storage directory, so sharding multiplies leftover temp directories.

## Issue Context
- The sharded `.test` script executes 5 independent Jest processes.
- Each process runs the with-registry preset’s `globalSetup`, which always creates a new temp storage directory and exports its path via `PNPM_REGISTRY_MOCK_STORAGE`.
- `globalTeardown` should remove that directory (optionally behind an env flag to keep it for debugging).

## Fix Focus Areas
- __utils__/jest-config/with-registry/globalTeardown.js[1-3]
- __utils__/jest-config/with-registry/globalSetup.js[16-29]
- installing/deps-installer/package.json[56-57]

## Suggested implementation direction
1. In `globalTeardown`, after `await global.killServer?.()`, read `process.env.PNPM_REGISTRY_MOCK_STORAGE` and recursively delete it (e.g., `fs.rmSync(storage, { recursive: true, force: true })`), guarding against missing/empty values.
2. Consider adding an opt-out env var like `PNPM_REGISTRY_MOCK_KEEP_STORAGE=1` for debugging.
3. Ensure deletion happens even if server kill fails (best-effort cleanup).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

• Split @pnpm/installing.deps-installer Jest run into 5 sequential shards to reduce OOM risk.
• Run each shard in a fresh Node/Jest process while keeping the registry-mock port setup.
• Teach .meta-updater to generate the new sharded test scripts in package manifests.

The following are alternative approaches to this PR:

Recommendation: The PR’s approach (sequential sharded Jest invocations) is the most robust way to avoid heap accumulation because it guarantees a fresh Node/Jest process per shard while preserving the existing registry-mock behavior. Consider heap-size tweaks only as a fallback if sharding alone is insufficient.

package.json Shard deps-installer '.test' into 5 sequential Jest runs +2/-1

Shard deps-installer '.test' into 5 sequential Jest runs

• Updates the package’s '.test' script to run Jest as five shards sequentially and adds a '.test:shard' helper script that encapsulates the registry-mock and NODE_OPTIONS setup. Keeps 'test' as 'pn compile && pn .test' so behavior remains consistent while reducing OOM risk.

installing/deps-installer/package.json

---

index.ts Generate sharded deps-installer Jest scripts via meta-updater +3/-1

Generate sharded deps-installer Jest scripts via meta-updater

• Introduces a shard-count constant and changes @pnpm/installing.deps-installer’s generated '.test' script to run 5 sequential shard invocations. Adds a new '.test:shard' script that performs the actual Jest call with the required registry-mock port and Node options.

.meta-updater/src/index.ts

---