Uncaught Error: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.

[Dominic-github]

[browser] Uncaught Error: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.
at Home (src/app/page.tsx:94:11)
92 |
93 | )}

94 |
| ^
95 |
96 |
97 | {welcomeOpen && <WelcomeModal onClose={() => setWelcomeOpen(false)} />}

[lefarcen]

Hi @Dominic-github — thanks for the clear stack trace. The pointer to src/app/page.tsx:94 is the ConvertChip render path, and this matches an already-tracked hook-order crash in #26.

I checked the current source: src/components/convert-chip.tsx returns null when the layout is not split before later hooks (useCallback / useEffect) run, so toggling layouts can change the hook count and trigger React's “Rendered fewer hooks than expected” error. There are already two open PRs for this exact slice (#28 and #30); we'll track which one lands there and keep this issue linked so your report doesn't get lost.

I’ve labeled this as a bug. 🙌

[lefarcen]

Quick update: PR #45 is now open for this ConvertChip hook-order crash. It moves the non-split layout guard below the hook calls, which matches the Rendered fewer hooks than expected failure path reported here.

There are also overlapping open fixes (#28 and #30), so we'll keep this issue open while maintainers decide which implementation lands and verify the crash is resolved.

[lefarcen]

Quick update: PR #52 also includes a focused ConvertChip hook-order fix for this “Rendered fewer hooks than expected” crash by moving the non-split layout guard below the hook calls.

It overlaps with the existing hook-order PRs (#28 and #30) and the broader parser/UI compatibility PR #50, so we’ll keep this issue open while maintainers compare the approaches and pick what lands.

[lefarcen]

Hey @Dominic-github — quick update on this one: the focused hook-order fix has landed on main via PR #28.

I rechecked the current ConvertChip source, and the non-split layout guard now runs after the hooks, with the keyboard shortcut effect gated internally for non-split mode. That matches the failure path from your Rendered fewer hooks than expected stack trace.

Could you update to the latest version and confirm whether this is gone in your setup? If it still reproduces, please share the exact version/commit and the layout switch path you clicked so we can keep digging.