fix: make Tevm examples release-ready - #1
Open
roninjin10 wants to merge 2 commits into
Open
Conversation
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
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.
What changed
Verified locally
Environment: Node 24.12.0, pnpm 9.15.9, Foundry 1.5.1.
pnpm install --frozen-lockfile— passed from a clean installpnpm lint— passed (394 files; one Biome deprecation info)pnpm typecheck— passedpnpm build— passed for Bun, esbuild, MUD contracts/client, Next, SvelteKit, and Vitepnpm test— passed: Bun 1 passed/1 RPC test skipped; esbuild 1 passed/1 RPC test skipped; MUD Forge 2 passed; Next 3 passed; Svelte 1 passed; Vite 1 passedpnpm docs:build— passed; Vocs generated 35 files and a sitemap for examples.tevm.shactionlintandgit diff --check— passedpnpm changeset status— next public versions: Bun 0.0.2, esbuild 0.0.2, MUD 0.0.1, Next 0.0.2, Svelte Ethers 0.1.4, Vite 0.0.2npm view— all referenced Tevm versions exist; all six new package names currently return E404 and are availableKnown external requirements
@tevm/mudis still unpublished. The MUD browser client compiles via an optional peer plus temporary ambient declarations/externalization, but cannot load that package at runtime until it is published.NPM_TOKENbefore merging a release PR.VERCEL_TOKEN,VERCEL_ORG_ID, andVERCEL_PROJECT_ID, and connectexamples.tevm.sh; the domain currently returns VercelDEPLOYMENT_NOT_FOUND.RPC_URL/RPC_URL_MAINNET; offline smoke tests now always run.