Skip to content

Update dependencies and remove Bun lockfile#229

Open
radiantjade wants to merge 1 commit into
tscircuit:mainfrom
radiantjade:update-deps-no-bun-lock
Open

Update dependencies and remove Bun lockfile#229
radiantjade wants to merge 1 commit into
tscircuit:mainfrom
radiantjade:update-deps-no-bun-lock

Conversation

@radiantjade
Copy link
Copy Markdown

Fixes #79

This updates the frontend/tooling and tscircuit ecosystem packages to current versions, removes the checked-in bun.lock, and keeps the existing bunfig.toml lockfile-saving-disabled behavior intact.

A couple of follow-up fixes were needed after the update:

  • migrated biome.json to the Biome 2 config shape
  • removed vite-tsconfig-paths and enabled Vite 8 native resolve.tsconfigPaths
  • added root @tscircuit/props so the latest tscircuit / @tscircuit/core exports resolve correctly during build

Verification:

  • bunx biome format --write vite.config.ts package.json biome.json
  • rm -rf node_modules dist && bun install && test ! -f bun.lock && bun run build

The build succeeds locally and bun.lock is not regenerated after a fresh install.

/claim #79

Issue tscircuit#79 asks for the dependency set to be moved forward while avoiding a checked-in Bun lockfile for Vercel deploys. This updates the frontend and tscircuit ecosystem packages, migrates Biome config for the new major version, removes the tracked bun.lock, and switches Vite path resolution to the native Vite 8 option.

Constraint: bunfig.toml already disables lockfile saving, so the tracked bun.lock had to be removed rather than regenerated.
Constraint: Latest tscircuit resolved an older root @tscircuit/props without a direct dependency, so @tscircuit/props is pinned at the root to satisfy core exports during Vite builds.
Rejected: Leave vite-tsconfig-paths installed | Vite 8 warns that path resolution is now native.
Confidence: medium
Scope-risk: moderate
Tested: bunx biome format --write vite.config.ts package.json biome.json
Tested: rm -rf node_modules dist && bun install && test ! -f bun.lock && bun run build
Not-tested: Vercel cloud deployment.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 15, 2026

@radiantjade is attempting to deploy a commit to the tscircuit Team on Vercel.

A member of the Team first needs to authorize it.

@radiantjade
Copy link
Copy Markdown
Author

Demo/verification video for the claim record: https://github.com/radiantjade/circuitjson.com/releases/download/circuitjson-229-demo-20260515/circuitjson-229-demo.mp4

It summarizes the dependency update, lockfile behavior, local build verification, and the external Vercel team-authorization blocker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update dependencies (runframe, circuit-json etc.) to latest version and confirm vercel deployment works

1 participant