From 50253cfa22ff81eda5499a3a20866d21b0ab1e17 Mon Sep 17 00:00:00 2001 From: JPeer264 Date: Mon, 14 Sep 2026 13:58:45 +0200 Subject: [PATCH] docs(nitro): Add serverDir so Nitro finds the verify route Nitro 3 defaults to `serverDir: false` and scans no directory, so a Nitro app built from this guide answered 404 on every route, `/debug-sentry` included, and sent no event. Set `serverDir: "./server"` in both config tabs and put the verify handlers under `server/routes/`, matching the `nitro-3` e2e app, which passes `withSentryConfig({ serverDir: './server' })` and keeps its handlers there. Refs SDK-1517 Co-Authored-By: Claude Opus 5 --- docs/platforms/javascript/guides/nitro/index.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/platforms/javascript/guides/nitro/index.mdx b/docs/platforms/javascript/guides/nitro/index.mdx index 0b3e77ec284da..ee35cfb2d519c 100644 --- a/docs/platforms/javascript/guides/nitro/index.mdx +++ b/docs/platforms/javascript/guides/nitro/index.mdx @@ -88,6 +88,7 @@ import { defineNitroConfig } from "nitro/config"; import { withSentryConfig } from "@sentry/nitro"; const config = defineNitroConfig({ + serverDir: "./server", // your Nitro options... }); @@ -108,6 +109,7 @@ export default defineConfig({ nitro( withSentryConfig( { + serverDir: "./server", // your Nitro options... }, { @@ -205,7 +207,7 @@ Add a test route that throws an error, then open `/debug-sentry` in your browser -```javascript {filename: routes/debug-sentry.ts} +```javascript {filename: server/routes/debug-sentry.ts} import { defineHandler } from "nitro/h3"; export default defineHandler(() => { @@ -230,7 +232,7 @@ To verify tracing, add a handler that starts a manual span: -```javascript {filename: routes/debug-sentry.ts} +```javascript {filename: server/routes/debug-sentry.ts} import { defineHandler } from "nitro/h3"; import * as Sentry from "@sentry/nitro";