You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated to I updated next to 13 & blitz to beta 21, and this resulted in an error at first render:
TypeError: Cannot read properties of null (reading 'useContext')
I've changed all instances of useRouter to import from 'next/navigation', as instructed:
import { useRouter } from "next/navigation"
And all files in this render tree have 'use client' at the top.
What else am I missing?
Paste all your error logs here:
event - compiled client and server successfully in 4.8s (1317 modules)
wait - compiling /404 (client and server)...
event - compiled client and server successfully in 305 ms (1307 modules)
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
TypeError: Cannot read properties of null (reading 'useContext')
at Object.useContext
at Object.useRouter
at BlitzProvider
at renderWithHooks
at renderIndeterminateComponent
at renderElement
at renderNodeDestructiveImpl
at renderNodeDestructive
at renderIndeterminateComponent
at renderElement
What is the problem?
I updated to I updated next to 13 & blitz to beta 21, and this resulted in an error at first render:
I've changed all instances of useRouter to import from 'next/navigation', as instructed:
And all files in this render tree have
'use client'
at the top.What else am I missing?
Paste all your error logs here:
Paste all relevant code snippets here:
n/a
What are detailed steps to reproduce this?
Run
blitz -v
and paste the output here:The text was updated successfully, but these errors were encountered: