mirror of
https://github.com/lukevella/rallly.git
synced 2025-04-30 18:56:45 +02:00
🔥 Remove global-error from landing page
This was causing issues on localhost
This commit is contained in:
parent
696505bce8
commit
f7d8033c96
1 changed files with 0 additions and 23 deletions
|
@ -1,23 +0,0 @@
|
||||||
"use client";
|
|
||||||
|
|
||||||
import * as Sentry from "@sentry/nextjs";
|
|
||||||
import NextError from "next/error";
|
|
||||||
import { useEffect } from "react";
|
|
||||||
|
|
||||||
export default function GlobalError({ error }: { error: Error & { digest?: string } }) {
|
|
||||||
useEffect(() => {
|
|
||||||
Sentry.captureException(error);
|
|
||||||
}, [error]);
|
|
||||||
|
|
||||||
return (
|
|
||||||
<html>
|
|
||||||
<body>
|
|
||||||
{/* `NextError` is the default Next.js error page component. Its type
|
|
||||||
definition requires a `statusCode` prop. However, since the App Router
|
|
||||||
does not expose status codes for errors, we simply pass 0 to render a
|
|
||||||
generic error message. */}
|
|
||||||
<NextError statusCode={0} />
|
|
||||||
</body>
|
|
||||||
</html>
|
|
||||||
);
|
|
||||||
}
|
|
Loading…
Add table
Reference in a new issue