Questify

3.18.1

Released

Fixes

  • An error on a page with no error screen of its own — sign-up, sign-in, onboarding, the public and invitation pages, or the root layout — now shows Questify's "Something went wrong" panel and is reported, instead of Next's bare "Application error" screen with nothing recorded. The root boundary (global-error.tsx) rendered the shared panel, whose "Try again" called useRouter(); Next mounts that boundary outside the app router, so the hook threw and took the boundary down with it (Sentry WEB-1, on /auth/signup). It now renders RootErrorPanel, which uses no router: "Try again" reloads the page and the home link is a full page load. The (app) and admin boundaries are unchanged (#1081).

Technical changes· 2 entries for database, tooling, CI, tests and docs

Tests

  • global-error.test.tsx renders the root boundary against the real next/navigation rather than a mocked router, which is what had hidden the crash, and pins the reload on "Try again", the digest reference and the home link (#1081).

Documentation

  • docs/ops/error-monitoring.md names RootErrorPanel as the root boundary's reporter (#1081).