Migrate RunesSwap to TanStack Start and Cloudflare Workers

[robin-liquidium]

Replace Next.js with TanStack Start and deploy the existing swap, borrowing, portfolio, transactions, rune information, and documentation screens on Cloudflare Workers. Existing API paths and response shapes remain compatible. The Worker is live at https://runesswap.robin-obermaier.workers.dev; production DNS cutover is pending registrar nameserver changes.

The migration removes redundant query/API/SDK wrappers and forwarding-only tests while retaining financial, wallet, authentication, and signing coverage. The SatsTerminal SDK uses native fetch through a pinned Bun patch because its node-fetch transport fails in workerd. BTC pricing now uses mempool.space because CoinGecko rejects Worker requests. Server credentials are Worker secrets and are absent from client bundles. Cloudflare Web Analytics replaces Vercel Analytics with SPA tracking; its public beacon token is embedded in production HTML.

Validation: full ai-check passes (28 suites, 208 tests; lint, formatting, architecture checks, strict TypeScript, unused-code checks, and production build). Deployed page/static-asset/API smoke checks pass, including live rune data, prices, chart timeframes, wallet selection, and navigation. Live BTC balance, transaction history (100 events), and portfolio aggregation (17 rune balances with metadata and market data) also return successful responses for the public documentation address. A read-only quote returns the same no-orders response as Vercel. Real wallet signing, swaps, borrowing, and repayment remain part of owner verification. Two full repository reviews confirmed the API/runtime migration. Follow-up changes retain original SDK errors in server logs, restore chart/tab loading feedback and lazy icons, correct stale documentation, and remove unused framework assets. The review suggestion to restore relative README links was rejected because browser verification showed those links break in /docs. Trailing-slash URLs were tested: /swap/ redirects and /api/popular-runes/ succeeds. Local review-helper and CodeRabbit coverage were unavailable; GitHub OpenCode supplied the full reviews.

Keep the existing Vercel project and production deployment for rollback until owner verification is complete. vercel.json disables new Git deployments of the migrated app. DNS setup, custom-domain cutover, and rollback instructions are in docs/cloudflare-migration.md.

[coderabbitai]

Important

Review skipped

Too many files!

This PR contains 158 files, which is 58 over the limit of 100.

To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch.

Upgrade to a paid plan to raise the limit.

This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 0d2b7ba9-568c-48c5-bc03-edb79eaf12da

📥 Commits

Reviewing files that changed from the base of the PR and between 0b6e029 and 65f8377.

⛔ Files ignored due to path filters (7)

• bun.lock is excluded by !**/*.lock
• public/favicon.ico is excluded by !**/*.ico
• public/file.svg is excluded by !**/*.svg
• public/globe.svg is excluded by !**/*.svg
• public/next.svg is excluded by !**/*.svg
• public/vercel.svg is excluded by !**/*.svg
• public/window.svg is excluded by !**/*.svg

📒 Files selected for processing (158)

• .env.example
• .github/workflows/main-build.yml
• .github/workflows/pr-ci.yml
• .gitignore
• AGENTS.md
• CHANGELOG.md
• README.md
• biome.json
• docs/cloudflare-migration.md
• jest.config.mjs
• jest.setup.js
• knip.json
• next.config.ts
• package.json
• patches/@satsterminal-sdk%2Fcore@1.6.31.patch
• scripts/jest-environment.cjs
• scripts/lint-architecture.mjs
• scripts/run-next-build.sh
• src/app/api/btc-price/route.test.ts
• src/app/api/btc-price/route.ts
• src/app/api/popular-runes/route.test.ts
• src/app/api/popular-runes/route.ts
• src/app/borrow/page.tsx
• src/app/docs/page.tsx
• src/app/error.tsx
• src/app/global-error.tsx
• src/app/globals.css
• src/app/layout.tsx
• src/app/not-found.tsx
• src/app/page.tsx
• src/app/portfolio/page.tsx
• src/app/providers.tsx
• src/app/runes-info/page.tsx
• src/app/swap/page.tsx
• src/app/your-txs/page.tsx
• src/components/borrow/BorrowSuccessMessage.tsx
• src/components/borrow/BorrowTab.tsx
• src/components/charts/PriceChart.tsx
• src/components/formatters/FormattedLiquidiumCollateral.tsx
• src/components/formatters/FormattedRuneAmount.tsx
• src/components/formatters/FormattedRuneName.tsx
• src/components/layout/AppInterface.tsx
• src/components/layout/FooterComponent.tsx
• src/components/layout/Layout.tsx
• src/components/layout/TabNavigation.tsx
• src/components/layout/TabPageLayout.tsx
• src/components/loading/Loading.tsx
• src/components/portfolio/PortfolioTab.tsx
• src/components/portfolio/YourTxsTab.tsx
• src/components/runes/RuneDetails.tsx
• src/components/runes/RuneIcon.tsx
• src/components/runes/RuneSearchBar.tsx
• src/components/runes/RunesInfoTab.tsx
• src/components/swap/AssetSelectorDropdown.tsx
• src/components/swap/InputArea.tsx
• src/components/swap/SwapStatusMessages.tsx
• src/components/swap/__tests__/InputArea.test.tsx
• src/components/ui/TitleText.tsx
• src/components/wallet/ConnectWalletButton.tsx
• src/components/wallet/WalletOptionsList.tsx
• src/components/wallet/WalletProvider.tsx
• src/context/BackgroundContext.tsx
• src/context/LaserEyesContext.tsx
• src/hooks/__tests__/useRuneDataHooks.test.ts
• src/hooks/__tests__/useRuneDataQuery.test.ts
• src/hooks/__tests__/useRuneDataQuery.test.tsx
• src/hooks/swapQuote/helpers.ts
• src/hooks/useApiQuery.ts
• src/hooks/useRuneDataQuery.ts
• src/lib/__tests__/apiUtils.test.ts
• src/lib/__tests__/liquidiumAuth.test.ts
• src/lib/__tests__/rateLimit.test.ts
• src/lib/__tests__/satsTerminalError.test.ts
• src/lib/__tests__/satsTerminalTransport.test.ts
• src/lib/__tests__/serverUtils.test.ts
• src/lib/apiResponse.ts
• src/lib/apiUtils.ts
• src/lib/liquidiumAuth.ts
• src/lib/popularRunes.ts
• src/lib/rateLimit.ts
• src/lib/satsTerminalError.ts
• src/lib/serverUtils.ts
• src/lib/supabase.ts
• src/lib/withApiHandler.ts
• src/routeTree.gen.ts
• src/router.tsx
• src/routes/__root.tsx
• src/routes/api.btc-price.ts
• src/routes/api.liquidium.auth.ts
• src/routes/api.liquidium.borrow.prepare.ts
• src/routes/api.liquidium.borrow.quotes.ts
• src/routes/api.liquidium.borrow.ranges.ts
• src/routes/api.liquidium.borrow.submit.ts
• src/routes/api.liquidium.challenge.ts
• src/routes/api.liquidium.portfolio.ts
• src/routes/api.liquidium.repay.ts
• src/routes/api.ordiscan.btc-balance.ts
• src/routes/api.ordiscan.list-runes.ts
• src/routes/api.ordiscan.rune-activity.ts
• src/routes/api.ordiscan.rune-balances.ts
• src/routes/api.ordiscan.rune-info-by-id.ts
• src/routes/api.ordiscan.rune-info.ts
• src/routes/api.ordiscan.rune-market.ts
• src/routes/api.ordiscan.rune-update.ts
• src/routes/api.popular-runes.ts
• src/routes/api.portfolio-data.ts
• src/routes/api.rune-price-history.ts
• src/routes/api.sats-terminal.psbt.confirm.ts
• src/routes/api.sats-terminal.psbt.create.ts
• src/routes/api.sats-terminal.quote.ts
• src/routes/api.sats-terminal.search.ts
• src/routes/borrow.tsx
• src/routes/changelog.tsx
• src/routes/docs.tsx
• src/routes/index.tsx
• src/routes/legal.tsx
• src/routes/portfolio.tsx
• src/routes/runes-info.tsx
• src/routes/swap.tsx
• src/routes/your-txs.tsx
• src/server.test.ts
• src/server.ts
• src/server/api/btc-price/route.test.ts
• src/server/api/btc-price/route.ts
• src/server/api/liquidium/auth/route.ts
• src/server/api/liquidium/borrow/prepare/route.ts
• src/server/api/liquidium/borrow/quotes/route.ts
• src/server/api/liquidium/borrow/ranges/route.ts
• src/server/api/liquidium/borrow/submit/route.ts
• src/server/api/liquidium/challenge/route.ts
• src/server/api/liquidium/helpers.ts
• src/server/api/liquidium/portfolio/route.ts
• src/server/api/liquidium/repay/route.ts
• src/server/api/ordiscan/btc-balance/route.ts
• src/server/api/ordiscan/helpers.ts
• src/server/api/ordiscan/list-runes/route.ts
• src/server/api/ordiscan/rune-activity/route.ts
• src/server/api/ordiscan/rune-balances/route.ts
• src/server/api/ordiscan/rune-info-by-id/route.ts
• src/server/api/ordiscan/rune-info/route.test.ts
• src/server/api/ordiscan/rune-info/route.ts
• src/server/api/ordiscan/rune-market/route.ts
• src/server/api/ordiscan/rune-update/route.ts
• src/server/api/popular-runes/route.test.ts
• src/server/api/popular-runes/route.ts
• src/server/api/portfolio-data/route.test.ts
• src/server/api/portfolio-data/route.ts
• src/server/api/rune-price-history/route.ts
• src/server/api/sats-terminal/psbt/confirm/route.ts
• src/server/api/sats-terminal/psbt/create/route.ts
• src/server/api/sats-terminal/quote/route.ts
• src/server/api/sats-terminal/search/route.test.ts
• src/server/api/sats-terminal/search/route.ts
• src/test-utils.ts
• tsconfig.json
• vercel.json
• vite.config.ts
• wrangler.jsonc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[opencode-agent]

PR Review: Migrate RunesSwap to TanStack Start and Cloudflare Workers

I reviewed the full diff (159 files) against base 0b6e029, including the new Worker entry, all 24 API route adapters, the ported server handlers, the client migration, config/CI changes, and the new tests. Overall this is a careful, well-executed migration: API paths/methods/response envelopes are preserved (I verified every adapter's HTTP method against the old Next.js handlers), behavior of useRuneDataQuery/useApiQuery is equivalent, the BTC price route keeps its cache/stale-fallback semantics, secrets stay out of the client bundle, and the docs.tsx/changelog.tsx ?raw bundling correctly replaces runtime fs reads that would never work in workerd. The server.ts apex redirect and its test are clean.

Bugs / issues to address

1. src/lib/satsTerminalError.ts — the new ReferenceError branch swallows genuine bugs without logging. In production, createErrorResponse logs only the new generic message (details is undefined), so the original ReferenceError/apiKey is not defined error is lost entirely — every code bug of that type in the quote/PSBT pipeline becomes an untraceable "External service error". Matching on message text is also fragile. Suggest logging the original error (e.g. logger.error(..., { error })) before returning the generic response, or narrowing the match.

2. Analytics silently dropped. @vercel/analytics was removed from layout.tsx and package.json with no mention in the CHANGELOG or PR body. If intentional, say so in the changelog; if not, add Cloudflare Web Analytics or reinstate a beacon before cutover, or you'll lose traffic data from day one.

3. Stale AGENTS.md testing docs. It still says "Unit tests use Jest with the ts-jest preset", but this PR switches to @swc/jest with a custom jsdom environment. Per the repo's own rules, AGENTS.md must be updated when workflows change.

4. Contradictory CHANGELOG. The same ## [Unreleased] → Changed section now contains both "Migrated the application from Next.js…" and the older "Refreshed Next.js 16.3.4 … to current stable releases". The stale line should be removed/reworded when this merges.

5. src/app/error.tsx stale comment: "Route-level error boundary for App Router segments" — Next.js-ism left behind.

Security observations (no leaks found, one hardening suggestion)

• Verified no client-importable module reads server secrets: supabase.ts, liquidiumSdk.ts, serverUtils.ts, liquidiumAuth.ts are only reachable from src/server/api/** and tests; client code uses only import.meta.env.VITE_QUOTE_MOCK_ADDRESS. ✅
• handleApiError still returns details: error.stack in the response body in production (only logging of details is prod-gated). Pre-existing, carried over verbatim — worth fixing separately since stack traces to clients are an info-leak.
• The rate limiter now trusts cf-connecting-ip first — correct behind Cloudflare (including workers.dev), and there's a test for it. ✅
• Hardening suggestion: nothing in lint-architecture.mjs prevents a client component from importing @/server/api/..., @/lib/supabase, or @/lib/serverUtils — an accidental import would break the client bundle (process undefined) or worse. Given this PR's "secrets absent from client bundles" guarantee, add a forbidden-pattern rule for server-only imports outside src/server / src/routes/api.*.

Minor improvements

• .gitignore .env* is overly broad — it would also ignore a future .env.example if it weren't already tracked. Prefer .env, .env.*, !.env.example.
• README links to docs/cloudflare-migration.md use absolute URLs pointing at the robin-liquidium fork — they'll be wrong if merged upstream to ropl-btc. Use relative links (also works better in the in-app /docs page).
• Leftover Next.js boilerplate in public/: next.svg, vercel.svg, file.svg, globe.svg, window.svg are unused (Bitcoin.svg is used by src/types/common.ts).
• Tab loading UX regression: per-tab next/dynamic loading messages ("Loading borrow tab…", "Loading chart…") collapsed into one generic "Loading application…" in TabPageLayout. Acceptable, but restoring per-tab fallbacks in AppInterface's lazy boundaries would be cheap.
• og:url/twitter:image point to apex https://runesswap.app while the Worker 308s apex → www. Make og:url the canonical www URL (pre-existing, but the new redirect makes it more relevant).
• 24 near-identical route adapters are inherent to file-based routing; a tiny apiHandlers({ GET, POST }) helper could DRY the ({ request }) => GET(request) boilerplate. Optional.
• Pre-existing, carried over: searchRunesViaSupabase interpolates user input into a PostgREST .or() string (only %/_ stripped); ,/(/) in the query can alter filter logic. Worth a follow-up sanitize since it's user-controlled.

Verification note

I could not run bun run ai-check locally (no Bun/deps in this environment), so I'm relying on the reported CI pass (28 suites / 207 tests). Static review of types found no issues: exhaustive switch in AppInterface is sound, cf cache options in rune-price-history pass as a non-literal variable, and the Bun patch correctly preserves the SDK's node_fetch_1.default(...) call shape.

Verdict: Approve with changes — items 1–4 should be fixed before merge; the rest are follow-ups. The rollout plan (Vercel kept for rollback, vercel.json guard, documented DNS cutover) is solid.

opencode session  |  github run

[opencode-agent]

PR Review: Migrate RunesSwap to TanStack Start and Cloudflare Workers

Summary

This is a well-executed migration. I verified the move by diffing old src/app/api/** handlers against the new src/server/api/** handlers with NextRequest/NextResponse renamed — the business logic is essentially verbatim, and all 24 API paths map 1:1 to the old URL structure. The consolidation of error handling (removed SDK wrapper → extended handleSatsTerminalError) preserves coverage across quote/search/PSBT routes, and the new tests (satsTerminalTransport, server.test, rateLimit, useRuneDataQuery) target exactly the risky seams of the migration.

Approval-worthy, with a few low-severity items below.

What I verified

• No secret leakage: only VITE_QUOTE_MOCK_ADDRESS (a public read-only address) is client-exposed; no client component imports supabase/serverUtils/liquidiumSdk.
• Suspense/SSR correctness: TabPageLayout wraps the lazy tab components in <Suspense>; RepayModal got its own boundary; ClientOnly + lazy(createClientOnlyFn(...)) correctly keeps LaserEyes out of SSR.
• useRuneDataQuery parity: old useApiQuery defaulted staleTime: Infinity — preserved.
• SDK patch: node-fetch → globalThis.fetch in @satsterminal-sdk/core, pinned and covered by a transport test asserting auth header and payload shape.
• CI: both workflows now run full ai-check (PR CI previously skipped build) with no trigger overlap.
• Docs discipline: AGENTS.md, README, CHANGELOG, and a thorough migration/rollback doc are all updated.

Findings

Low

1. Rate limiting is weaker on Workers (src/lib/rateLimit.ts). The in-memory Map is per-isolate, and Workers isolates churn constantly and vary by colo — so the Liquidium auth and rune-update limits are now much easier to slip past than on Next/Vercel. The "best-effort" comment is honest, but for the authenticated/financial endpoints consider Cloudflare-native rate limiting (WAF rules or the rate-limiting binding) as a follow-up.

2. og:url points to the redirecting apex (src/routes/__root.tsx). og:url is https://runesswap.app, but src/server.ts 308-redirects apex → www. Crawlers/validators prefer the canonical URL; suggest https://www.runesswap.app (same for the og/twitter image URLs for consistency).

3. Trailing-slash behavior change. Next matched /api/ordiscan/list-runes/; TanStack Router's default trailing-slash handling won't. Low risk for your own UI, but any external consumer appending / gets a 404/redirect. Worth a smoke check post-cutover.

4. .gitignore .env* also matches .env.example (harmless since it's tracked, but confusing). Consider adding !.env.example.

Nits (mostly pre-existing)

5. src/app/error.tsx — comment still says "App Router segments".
6. src/server/api/sats-terminal/quote/route.ts — JSON.stringify(error) inside the error handler would throw on circular error objects, escaping withApiHandler (pre-existing pattern, unchanged).
7. RuneIcon — remote unisat icons lost next/image's built-in lazy loading; consider loading="lazy" on the <img> for long dropdown lists.
8. src/lib/supabase.ts — persistSession: true on a server/Worker client just triggers supabase-js's "no storage" warning; persistSession: false would be cleaner (pre-existing).

Notes

• The removed default: case in AppInterface's tab switch is safe — the ActiveTab union makes the switch exhaustive, and TypeScript enforces it.
• vercel.json disabling Git deployments lands on main too; that's intentional and documented in docs/cloudflare-migration.md, and rollback doesn't depend on new Vercel builds. Good call keeping the doc's DNS/rollback table.
• I reviewed statically; the environment here has no installed dependencies, so I'm trusting the reported ai-check (28 suites / 207 tests) results, which the PR CI now reproduces on every push.

Nice work on keeping this a pure, verifiable migration with no behavioral drift in the API layer.

opencode session  |  github run

[opencode-agent]

PR Review: Migrate RunesSwap to TanStack Start and Cloudflare Workers

I reviewed the full migration diff (0b6e029..65f8377, ~160 files) plus the three follow-up commits, and verified the runtime-sensitive claims externally where possible. No deps in this environment, so I couldn't re-run ai-check; this is a static + live-endpoint review.

Previous review rounds — verified resolved

• satsTerminalError.ts ReferenceError branch now calls logApiError before returning the generic 500, with a test asserting the original message/stack reach the logs. ✅
• Analytics: Cloudflare Web Analytics is wired up and documented in the CHANGELOG. I verified the two things that could have silently broken it:
  • static.cloudflareinsights.com/beacon.min.js serves Access-Control-Allow-Origin: *, so the unusual type="module" attribute won't fail on CORS (module scripts are CORS-mode, unlike classic scripts).
  • The beacon source shows spa defaults to HistoryAndNavigationAPI when absent, so {"token":"..."} without "spa": true still tracks TanStack Router client-side navigations. ✅
• AGENTS.md updated (@swc/jest), CHANGELOG Next.js lines re-contextualized, .gitignore has !.env.example, boilerplate SVGs removed, error.tsx stale comment gone, per-tab loading messages + chart Suspense restored, RuneIcon has loading="lazy", og:url now points at www. ✅
• swap.tsx repeated-param fix (?rune=A&rune=B → first wins) is correct for TanStack's default search parser, which produces arrays for repeated keys. ✅

Findings (all low severity — nothing blocking)

1. Possible analytics ID mismatch — docs/cloudflare-migration.md:9 documents "Site ID: d5422c3e…" but the token embedded in src/routes/__root.tsx:70 is b0a6014e…. If the doc's "Site ID" was copied from the same dashboard snippet as the token, one of them is wrong and beacons could land in a different Web Analytics property. If they're intentionally two different identifiers (site object ID vs. beacon token), a parenthetical would prevent future confusion. Worth a 30-second dashboard check.

2. Beacon fires on preview deployments — it's gated only on import.meta.env.PROD, so every deployed workers.dev build reports pageviews into the production property. Cloudflare records hostname so you can filter, but if you want clean prod numbers, gate on location.hostname or use a separate token for previews.

3. handleApiError still leaks error.stack in the response body (apiUtils.ts:41, carried over pre-migration). Only logging of details is prod-gated; the details field goes to clients in production. Now that this Worker is about to be the production origin, worth the small follow-up fix (drop details from fail() when NODE_ENV === 'production').

4. No client/server import guard in lint-architecture.mjs — suggested in round 1, not added. Today it's safe (client files only use import type from runesData/runeMarketData, which I verified), but a single forgotten type keyword in a client component would bundle supabase.ts/serverUtils.ts into the client chunk. A one-line forbidden-pattern rule (from '@/server/, from '@/lib/(supabase|serverUtils|liquidiumSdk)' outside src/server, src/routes/api.*, and tests) would make the "secrets absent from client bundles" guarantee self-enforcing.

5. Nits

   • og:image/twitter:image (__root.tsx:28,32) still use the apex URL that now 308-redirects; crawlers generally follow, but www would match og:url.
   • quote/route.ts:46 — JSON.stringify(error) inside the custom error handler would itself throw on a circular error object and escape withApiHandler (pre-existing pattern, unchanged by this PR).
   • README links to docs/cloudflare-migration.md are absolute and point at the robin-liquidium fork — correct for this repo, but they'll reference the fork if merged into ropl-btc upstream. (Keeping them absolute for in-app /docs rendering is the right call; just swap the org on merge.)
   • In-memory rate limiting is per-isolate on Workers, so it's looser than before in practice. Parity-wise acceptable as "best-effort"; consider a Cloudflare rate-limiting rule for the Liquidium auth endpoint as a follow-up.

Verdict

Approve. All blocking items from the two earlier reviews are addressed with tests, and the remaining findings are follow-ups. The migration itself is faithful: handlers diff clean against their Next.js predecessors, response envelopes and API paths are preserved, secrets stay server-side, and the rollout/rollback plan (Vercel retained, vercel.json guard, documented DNS cutover) is sound. Items 1 and 3 are the two I'd most want done before or shortly after DNS cutover.

opencode session  |  github run