Files
donghyeon-kaandClaude Opus 5.5 a8520f6dfb fix(fixtures): keep pnpm in a linked fixture from installing (F-4)
pnpm verifies the install before a script, and a fixture running it with
CI=true against an install made without CI saw other settings and installed
through the linked .pnpm and .bin, rewriting the shared lock.yaml and shims.
Every fixture pnpm run now turns that check off; a test pins it for all.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 13:20:12 +09:00

79 lines
3.4 KiB
TypeScript

import { copyFile, mkdir, readdir, readFile, stat, symlink, writeFile } from "node:fs/promises";
import path from "node:path";
/**
* Links the repository's installed dependencies into a throwaway fixture root.
*
* The obvious form — one directory symlink at `<fixture>/node_modules` — is
* destructive. A fixture runs `pnpm` inside itself, pnpm does not recognise the
* modules directory it finds there, and its purge follows the symlink and
* deletes the *repository's* real dependencies mid-run. With `CI=true` that
* happens without a prompt, so a test suite silently uninstalls the workspace
* it is running in.
*
* `node_modules` is therefore a real directory here, and every entry inside it
* is an individual symlink. Package resolution is unchanged, but a recursive
* delete unlinks the fixture's own symlinks instead of walking through one link
* into the shared tree.
*
* Top-level files are pnpm's install state (`.modules.yaml`,
* `.pnpm-workspace-state-v1.json`, ...). pnpm rewrites them in place when it
* runs inside the fixture, so they are copied: a link would carry the fixture's
* path into the repository's own state and make its next pnpm command
* re-verify the install.
*
* The copied workspace state still names the repository as its validated
* project, so pnpm in the fixture would re-verify and start an install through
* the linked directories. It is rewritten to name the fixture root instead:
* the packages are the repository's own, already validated.
*/
/**
* F-4. The environment for every `pnpm` a linked fixture runs. pnpm verifies
* the install before a script and, when the fixture's copied state disagrees
* with its own settings (for example `CI=true` against an install made
* without it), installs. `.pnpm` and `.bin` are links into the repository's
* node_modules, so that install rewrote the shared `.pnpm/lock.yaml` and bin
* shims. A fixture started through `pnpm <script>` inherits this setting from
* pnpm; one started directly (`node scripts/run-vitest.ts run <file>`) did not.
* The fixture uses the repository's packages as they are; it never installs.
*/
export const FIXTURE_PNPM_ENVIRONMENT = Object.freeze({
pnpm_config_verify_deps_before_run: "false",
});
export async function linkFixtureNodeModules(
fixtureRoot: string,
sourceRoot: string = process.cwd(),
): Promise<void> {
const source = path.join(sourceRoot, "node_modules");
const target = path.join(fixtureRoot, "node_modules");
await mkdir(target, { recursive: true });
for (const entry of await readdir(source)) {
const from = path.join(source, entry);
const to = path.join(target, entry);
if ((await stat(from)).isDirectory()) await symlink(from, to, "dir");
else await copyFile(from, to);
}
await retargetWorkspaceState(
path.join(target, ".pnpm-workspace-state-v1.json"),
fixtureRoot,
);
}
async function retargetWorkspaceState(
statePath: string,
fixtureRoot: string,
): Promise<void> {
let state: { projects?: Record<string, unknown>; lastValidatedTimestamp?: number };
try {
state = JSON.parse(await readFile(statePath, "utf8"));
} catch {
return; // no state file, or not pnpm's JSON: nothing to retarget
}
const [project] = Object.values(state.projects ?? {});
if (project === undefined) return;
state.projects = { [fixtureRoot]: project };
state.lastValidatedTimestamp = Date.now();
await writeFile(statePath, `${JSON.stringify(state, null, 2)}\n`);
}