feat(bridge-ui-next): add Next.js port of bridge-ui - #21937
Draft
0xmapachex wants to merge 2 commits into
Draft
Conversation
Add packages/bridge-ui-next, a Next.js 16 (App Router) + React 19 port of the SvelteKit bridge-ui. The original bridge-ui is left untouched and remains the production app. - All 114 components, 144 libs, and 11 stores ported to React/TSX - Tailwind 3.4 + daisyUI 4 with the original themes, shadcn/ui, TanStack Query v5, wagmi v2/viem, react-i18next, Zustand - tsc --noEmit clean, next build green (7/7 routes) - Pixel-parity verified side-by-side for home and /transactions - Remaining work tracked in packages/bridge-ui-next/MIGRATION.md Also registers the package in the pnpm workspace and approves native build scripts via the new pnpm allowBuilds map. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… and test hardening Follow-up pass on the Next.js port: test-first correctness fixes (zustand replace semantics via createValueStore, TokenInput stale amount, Moralis per-wallet cache keying, StrictMode-safe wagmi watcher), port of upstream quota-exhaustion claim handling from bridge-ui (checkQuota, quotaManagerAbi, dialog wiring), /api/nft input validation and baseline security headers, removal of ~1,170 lines of dead React Query hooks, and unit tests up from 110 to 177 passing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
Summary
Adds
packages/bridge-ui-next— a 1:1 port of the Taiko Bridge web app from SvelteKit to Next.js (App Router), plus a post-port review/hardening pass. Seepackages/bridge-ui-next/MIGRATION.mdfor the full migration narrative and architecture notes.Commit 1 — the port
@web3modal/wagmibumped v4 → v5$libs/**business layer (bridge classes, proof, fee, relayer, token, chain, network) ported using@wagmi/coreactionsCommit 2 — review fixes & hardening
createValueStore; TokenInput one-keystroke-stale amount; Moralis NFT cache keyed perchainId:address(was shared across wallets); StrictMode-safe wagmi watcherbridge-uionmain(checkQuota,quotaManagerAbi, ClaimDialog/RetryDialog wiring, schema field) with upstream tests/api/nftinput validation (viemisAddress, positive-intchainId, 400 on bad JSON,Cache-Control: no-store); baseline security headers innext.config.ts; relayer axios timeoutsUnit tests: 177 passing (up from 110);
tsc --noEmitclean;next buildgreen.Still open (why draft)
CONFIGURED_*values<img>→next/imagemigration🤖 Generated with Claude Code