Skip to content

[CU-123vqc2bhh0] Commit build output and drop the prepare script - #2

Merged
billouboq merged 1 commit into
masterfrom
CU-123vqc2bhh0/commit-build-output
Sep 24, 2026
Merged

billouboq merged 1 commit into
masterfrom
CU-123vqc2bhh0/commit-build-output

Conversation

@billouboq

Copy link
Copy Markdown

Why

beedeez-main installs this fork from a git URL. When the package has a prepare/prepack script, pnpm installs its devDependencies with the fork's own package manager (via corepack) and builds it on every cold install. That work shows up in every CI pnpm install (CU-123vqc2bhh0, pnpm 12 migration).

What

  • Stop ignoring build/ and commit it.
  • Remove prepare (it ran npm run build: pnpm 8 install + KaTeX prebuild + tsc).

Verified: the committed output is byte-identical (diff -rq) to what beedeez-main currently gets from the install-time build.

Maintenance

After changing src/, run pnpm build and commit the output with it.

🤖 Generated with Claude Code

beedeez-main installs this fork from git. With a prepare script, pnpm installs
its devDependencies (under pnpm 8 via corepack) and rebuilds it on every cold
install. Shipping build/ in the repo makes the git install a plain extract.

After changing src/, run `pnpm build` and commit build/.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@billouboq
billouboq merged commit 7da034d into master Sep 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant