Skip to content

Fix federated-css e2e cache handling #4397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 24, 2025
Merged

Fix federated-css e2e cache handling #4397

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions federated-css/scripts/start-all.cjs
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,16 @@
const { spawn } = require('node:child_process');
const waitOn = require('wait-on');
const path = require('node:path');
const fs = require('node:fs');

const root = path.resolve(__dirname, '..');

// Ensure v8 compile cache writes go to a local ignored folder instead of polluting
// sibling workspaces (corepack/pnpm relies on this cache under the hood).
const v8CacheDir = path.join(root, '.cache', 'v8-compile-cache');
fs.mkdirSync(v8CacheDir, { recursive: true });
process.env.V8_COMPILE_CACHE_CACHE_DIR = v8CacheDir;

function run(cmd, args) {
return spawn(cmd, args, { stdio: 'inherit', cwd: root, shell: true });
}
Expand Down
Loading