Repository navigation
Frontend logs React hydration errors #520/#422 on /auth in production builds (pre-existing) #133
Description
Found on 28 Oct 2026, while browser-checking the #132 dependency update. It's pre-existing: the same errors appear with main's dependencies (9413fb8).
Opening /auth on a production build (NITRO_PRESET=node-server, started with node .output/server/index.mjs) logs these page errors in Chromium (Playwright):
Minified React error #520, twice;Minified React error #422: an error during hydration, which React recovered from by rendering on the client.
The page still works: the sign-in title and the tenant, username and password fields render, and / redirects to /auth when signed out. The errors suggest the server-rendered HTML and the client render differ. A likely cause is the ssr: false routes (/auth), or the suppressHydrationWarning time cells.
Proposed
Reproduce with a development build to get the full React messages. Fix the mismatch, and add a Playwright check that fails on page errors.
Done when
/auth and / load in a production build with no page errors, and the check proving it is attached here.
Generated by Claude Code
Activity
Merge pull request #136 from amar-python/fix/133-hydration
amar-python commentedon Oct 28, 2026
Evidence: no hydration errors on the product owner's machine. PR #136 merged at the product owner's direction on 28 Oct (
e2d232f). The test was run on Windows 10, Edge, atmainb21737baftergit pullandnpm ci, with the API and the Vite dev server running locally.The product owner signed out, cleared the console and loaded
http://localhost:8080/. The page went to/authwith a fresh load ([vite] connecting… / connected):Cannot read properties of undefined (reading 'routeId'), no React #520 and no #422. Before the fix, the dev server logged all three on this path.CS WAX not initialized(ContentIsolatedWorld.js) andAT-SDK disabled(ATContent.js) come from a browser extension's content scripts injected into the page, not from this repo.[tanstack-router] … SignInPage will not be code-splitwarning is a development-server bundling hint, not an error.This matches the production-build check on PR #136, where Chromium logged 8 errors before the fix and 0 after. Closing.
Generated by Claude Code