chore: update dependencies to latest versions (runframe, circuit-json, vite 8)#226
Open
GabrielSotto wants to merge 2 commits into
Open
chore: update dependencies to latest versions (runframe, circuit-json, vite 8)#226GabrielSotto wants to merge 2 commits into
GabrielSotto wants to merge 2 commits into
Conversation
…, vite, etc.) - Update @tscircuit/runframe to ^0.0.1946 (direct dep to avoid bun hoisting older core) - Update @tscircuit/props to ^0.0.533 (direct dep for courtyardCircleProps export) - Update tscircuit to ^0.0.1749, circuit-json to ^0.0.426, vite to ^8.0.12 - Update @vitejs/plugin-react to ^6.0.1 compatible with Vite 8/Rolldown - Update all other tscircuit packages, marked, posthog-js, tailwind-merge, etc. - Add bun.lock to .gitignore (bunfig.toml already has lockfile save=false) - Remove tracked bun.lock from git history Build verified: vite v8.0.12 ✓ built in 7.61s Dev server verified: VITE v8.0.12 ready in 317ms This contribution was assisted by Claude Code (Anthropic)
|
@GabrielSotto is attempting to deploy a commit to the tscircuit Team on Vercel. A member of the Team first needs to authorize it. |
…figPaths Vite 8 (Rolldown) supports tsconfig path resolution natively via resolve.tsconfigPaths. Remove the now-redundant plugin and use the native option instead, eliminating the deprecation warning. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Author
|
Updated: also migrated from the deprecated \�ite-tsconfig-paths\ plugin to Vite 8 native |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/claim #79
Closes #79
Summary
@tscircuit/runframeto^0.0.1946(added as direct dep to prevent bun from hoisting@tscircuit/[email protected]which lacked theSOLVERSexport required by newer runframe)@tscircuit/propsto^0.0.533(added as direct dep to ensurecourtyardCirclePropsis exported)tscircuitto^0.0.1749(latest)circuit-jsonto^0.0.426(latest)viteto^8.0.12+@vitejs/plugin-reactto^6.0.1(Vite 8 uses Rolldown)markedto^17.0.6,posthog-jsto^1.373.4,tailwind-mergeto^3.6.0,easyedato^0.0.269,circuit-json-to-*packages to latestbun.lockto.gitignore(repo already hadbunfig.tomlwith[install.lockfile] save = false)bun.lockfrom gitvite-tsconfig-pathsplugin to Vite 8 nativeresolve.tsconfigPaths— eliminates the deprecation warning from RolldownBuild verification
Dev server starts and renders the app without errors. The only warnings are non-blocking (chunk size, Three.js multiple instances — both pre-existing in the tscircuit ecosystem). No
vite-tsconfig-pathsdeprecation warning with the native option.This contribution was assisted by Claude Code (Anthropic)