Error boundary reset doesn't seem to work about next.js HOT 3 OPEN

@raulrpearson

I guess you want to render page.tsx in server side not client side, but reset function only re-render the Error boundary's content, and therefore server component generated in server side only re-render the same result.

An error component can use the reset() function to prompt the user to attempt to recover from the error. When executed, the function will try to re-render the Error boundary's contents. If successful, the fallback error component is replaced with the result of the re-render.

see doc https://nextjs.org/docs/app/building-your-application/routing/error-handling#recovering-from-errors
and code

I think you have to make api in backend somehow and add use client in your page.tsx and fetch the server result.

from next.js.

Did you try declaring "use client"; in page.tsx?

As per nextjs documentation here - https://nextjs.org/docs/app/building-your-application/rendering/client-components

"use client" is used to declare a boudary between a Server and Client Component modules. This means that by defining a "use client" in a file, all other modules imported into it, including child components, are considered part of the client bundle.

"use client" doesn't need to be defined in every component that needs to be rendered on the client. Once you define the boundary, all child components and modules imported into it are considered part of the client bundle.

from next.js.

Another workaround could be to use useRouter() from next/navigation and call router.refresh() in useEffect in error.tsx

from next.js.