Skip to content

Update circuitjson dependencies and remove Bun lockfile#240

Open
JacKane21 wants to merge 1 commit into
tscircuit:mainfrom
JacKane21:codex/circuitjson-deps-lockfile-79
Open

Update circuitjson dependencies and remove Bun lockfile#240
JacKane21 wants to merge 1 commit into
tscircuit:mainfrom
JacKane21:codex/circuitjson-deps-lockfile-79

Conversation

@JacKane21
Copy link
Copy Markdown

@JacKane21 JacKane21 commented May 22, 2026

Closes #79

/claim #79

Summary

  • update the tscircuit/circuit-json viewer, exporter, EasyEDA, STEP, and core tscircuit dependencies to the latest published versions checked from npm
  • remove the tracked bun.lock file
  • ignore future bun.lock and bun.lockb files while keeping the existing bunfig.toml [install.lockfile] save = false configuration
  • add vercel.json so Vercel uses the same Bun install/build path (bun install and bun run build) after the lockfile is removed

Validation

  • npm view checks for touched tscircuit/circuit-json package versions
  • npx --yes prettier@3.3.3 --check vercel.json package.json
  • git diff --check
  • npx --yes bun install (completed without regenerating bun.lock or bun.lockb)
  • npx --yes bun run build
  • prior validation on this branch: npm install --package-lock=false and npm run build

AI-assisted with Codex; I reviewed the diff and kept it scoped to dependency/build hygiene.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 22, 2026

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

A member of the Team first needs to authorize it.

@JacKane21
Copy link
Copy Markdown
Author

Quick status note: the only non-green item I can see is Vercel waiting for tscircuit team authorization on the fork deployment. I re-verified locally with both Bun and npm builds, and those validation commands are listed in the PR body.

@JacKane21 JacKane21 force-pushed the codex/circuitjson-deps-lockfile-79 branch from 9b4f9de to 723598f Compare May 22, 2026 13:15
@JacKane21
Copy link
Copy Markdown
Author

Updated this PR to keep the dependency refresh current and make the Vercel path explicit:

  • bumped the touched packages that moved since the first push (tscircuit and circuit-json-to-gerber) to the latest published versions I saw from npm
  • added vercel.json so Vercel uses bun install and bun run build after the lockfile is removed
  • re-ran npx --yes bun install and confirmed it did not regenerate bun.lock/bun.lockb
  • re-ran npx --yes bun run build successfully

The remaining non-green item is still Vercel waiting for tscircuit team authorization of the fork deployment.

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