Skip to content

Fix standalone CLI bundle build failing with data-liberation E404 #4101

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
sejas merged 1 commit into from
Jul 7, 2026
+8 −0
Merged

Fix standalone CLI bundle build failing with data-liberation E404 #4101

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
8 changes: 8 additions & 0 deletions scripts/create-standalone-bundle.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,14 @@ async function main(): Promise< void > {
// prod build, but `package:standalone` stamps `__IS_PACKAGED_FOR_STANDALONE__` so the
// curl-installed CLI identifies itself at runtime (update notifier + launch stats).
console.log( '==> Step 1/4: Building CLI package...' );
// install:bundle can run twice per CI job (the desktop make's forge hook runs
// it first). npm's --install-links re-resolves the changed data-liberation
// file: dep from the registry (E404) when reinstalling over that tree, so
// start from a clean node_modules, same as forge.config.ts does.
fs.rmSync( path.join( repoRoot, 'apps', 'cli', 'node_modules' ), {
recursive: true,
force: true,
} );
run( 'npm run cli:package:standalone' );

// Step 2: Assemble the bundle layout in a staging dir
Expand Down
Loading