The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 21, 2026 9:27am

PR Summary

Medium Risk
Medium risk because it changes render-time state updates and rAF-driven animation behavior in a hot UI path, which could affect cell rendering timing/perf if incorrect.

Overview
Prevents the table cell typewriter animation from briefly painting the full updated value by reworking useTypewriter to track the previous text in state (transactional under concurrent rendering) and derive the revealed substring from elapsed time during render.

The animation now uses a start-time ref plus a lightweight state “frame” tick to trigger re-renders, and adds guards for null/empty values so mount/scroll-in renders remain static while only subsequent updates animate.

^{Reviewed by Cursor Bugbot for commit e4f02aa. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

This PR fixes an intermittent full-value flash in the useTypewriter hook that occurred under React 18 concurrent rendering. The root cause was a useRef being used to track the previous text value: a discarded render would mutate the ref (prevTextRef.current = text) but roll back the setRevealed('') state update, causing the committed render to skip the reset and flash revealed ?? kind.text for one frame.

• Core fix: replaces prevTextRef (a useRef) with prevText (a useState), matching React's canonical "adjust state when a prop changes" pattern — state rolls back with discarded renders, guaranteeing the reset fires on the committed render.
• Defensive guard: adds text === null || text.length === 0 to the animation effect to protect against a stale animateRef from a discarded render, and removes the now-unnecessary as string cast since TypeScript narrows text correctly after the guard.

Confidence Score: 5/5

Safe to merge; the change is a targeted, well-reasoned fix to a single hook with no external side-effects.

The switch from useRef to useState for prevText correctly implements the documented React "adjust state when a prop changes" pattern and closes the concurrent-rendering gap described in the PR. animateRef.current is still mutated during render, but the committed render always re-evaluates the condition (because state rolled back), so the value is re-applied deterministically. The defensive text === null || text.length === 0 guard in the animation effect is sound. No logic regressions are apparent.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant React as React (Concurrent)
    participant Render as Render Phase
    participant State as State (prevText, revealed)
    participant Ref as animateRef (ref)
    participant Effect as useEffect [text]

    note over React: text prop changes A → B

    React->>Render: Start render (may be discarded)
    Render->>State: "prevText !== text → setPrevText(B), setRevealed('')"
    Render->>Ref: "animateRef.current = true"
    React-->>Render: Discard render (concurrent preempt)
    note over State: State rolls back (prevText=A, revealed=null)
    note over Ref: Ref keeps mutation: animateRef=true

    React->>Render: Committed render
    Render->>State: "prevText (A) !== text (B) → setPrevText(B), setRevealed('')"
    Render->>Ref: "animateRef.current = true (re-set)"
    React->>Render: "Re-render (state settled: prevText=B)"
    Render-->>React: "prevText===text, no-op"
    React-->>React: "Commit with revealed=''"

    React->>Effect: Fire (text dependency changed)
    Effect->>Ref: "animateRef.current? true → animateRef=false"
    Effect-->>React: Start rAF typewriter animation

_{Reviews (1): Last reviewed commit: "fix(table): typewriter prevText in state..." | Re-trigger Greptile}