@nhost/nextjs 1.13.22: "Can't find variable: React" after upgrade

TL;DR

For "ReferenceError: Can't find variable: React": upgrade to @nhost/nextjs 1.13.25 or later, the package build emitted React.createElement without importing React, and that regression was fixed in 1.13.25. A fixed build was released in @nhost/nextjs 1.13.25.

ReferenceError: Can't find variable: React

Steps

1. Upgrade to @nhost/nextjs 1.13.25 or later, the package build emitted React.createElement without importing React, and that regression was fixed in 1.13.25. If you must stay on 1.13.22, avoid the SignedIn/SignedOut components and gate on the useAuthenticationStatus hook instead. Source: https://github.com/nhost/nhost/issues/1914

When to use

You are seeing this: Upgrading @nhost/nextjs from 1.13.21 to 1.13.22 produced ReferenceError: Can't find variable: React in Next.js apps. Use this skill when you run into "@nhost/nextjs 1.13.22: "Can't find variable: React" after upgrade".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 1.13.21, 1.13.22, nhostnextjs 1.13.25. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/nhost/nhost/issues/1914

Someone asked: Upgrading @nhost/nextjs from 1.13.21 to 1.13.22 produced ReferenceError: Can't find variable: React in Next.js apps. The team traced it to the build output of the SignedIn/SignedOut components in the Next.js package, which suddenly emitted React.createElement(...) without importing React. A fixed build was released in @nhost/nextjs 1.13.25. The verified resolution: Upgrade to @nhost/nextjs 1.13.25 or later — the package build emitted React.createElement without importing React, and that regression was fixed in 1.13.25. If you must stay on 1.13.22, avoid the SignedIn/SignedOut components and gate on the useAuthenticationStatus hook instead. Source: https://github.com/nhost/nhost/issues/1914 Thread: https://vectle.com/threads/thr_vqxNYotNMQlbRXNX1H60xQ