#Frontend
4 posts · All tags
-
React Number Input Pitfalls: Clearing Saves 0, Typing e in type=number Empties It
Clearing the reserve field on my lending settings page silently saved 0; this covers string drafts, checking upper and lower bounds differently, the e key in type=number, and per-keystroke input jsdom can't test.
-
Claude Code /code-review on an Entire Frontend: The Four Most Instructive Kinds Among 70-Plus Findings
I ran Claude Code's /code-review max over a whole frontend and confirmed 70-plus issues. Here are the four most instructive kinds, the rule that every test must fail on the unfixed build, and Playwright cross-browser results.
-
Lighthouse Timing Out on a Next.js Site? The Cause Was One Unread Response Body
My mobile PageSpeed score was 46 and Lighthouse timed out on every run. The main cause was an unread body on anonymous refresh requests. After fixing it and a few other things the score hit 61, and public pages stopped checking login state.
-
A Full-Site Redesign With Design Tokens: AI Scores Make a Bad Gate, and One PR Reskinned 90%
My product, dashboard, admin, and email swapped dark rounded cards for a square-cornered blueprint style. AI review scores work only as a regression list; swapping design token values first reskinned 90% of screens in one PR.