05fd0e21ea
The withSentryConfig() wrapper caused recurring worker.js crashes in Next.js dev mode (vendor-chunks/lib/worker.js MODULE_NOT_FOUND). This crashed the server mid-request during image generation and other long-running operations. Fix: only apply withSentryConfig in production. In dev mode, use the raw Next.js config. Sentry instrumentation also gated to production only. Co-Authored-By: claude-flow <ruv@ruv.net>
20 lines
661 B
TypeScript
20 lines
661 B
TypeScript
export async function register() {
|
|
// Only load Sentry in production — the worker.js crash in dev mode
|
|
// (vendor-chunks/lib/worker.js MODULE_NOT_FOUND) makes the dev server unstable
|
|
if (process.env.NODE_ENV === "production") {
|
|
if (process.env.NEXT_RUNTIME === "nodejs") {
|
|
await import("../sentry.server.config");
|
|
}
|
|
if (process.env.NEXT_RUNTIME === "edge") {
|
|
await import("../sentry.edge.config");
|
|
}
|
|
}
|
|
}
|
|
|
|
export async function onRequestError(...args: unknown[]) {
|
|
if (process.env.NODE_ENV === "production") {
|
|
const Sentry = await import("@sentry/nextjs");
|
|
(Sentry.captureRequestError as Function)(...args);
|
|
}
|
|
}
|