Voeg Sentry-tunnel ook toe voor lokale development

Co-authored-by: Junie <junie@jetbrains.com>

src/main.tsx

@@ -22,11 +22,10 @@ if (sentryDsn) {
     enableLogs: true,
     // Ad-blockers/privacy extensions commonly block requests straight to *.ingest.sentry.io
     // (ERR_BLOCKED_BY_CLIENT), because it looks like third-party tracking. Routing through our
-    // own domain via a reverse-proxy "tunnel" avoids that (see nginx/reverse-proxy-nginx.conf.example).
-    // Only enabled for built (test/production) environments — local dev (`pnpm dev`) has no such
-    // proxy route available, so it keeps posting straight to Sentry (resolved by disabling the
-    // ad-blocker locally instead).
-    tunnel: import.meta.env.DEV ? undefined : '/sentry-tunnel',
+    // own domain via a "tunnel" avoids that: in built (test/production) environments this is
+    // handled by the reverse-proxy Pi (see nginx/reverse-proxy-nginx.conf.example); locally
+    // (`pnpm dev`) the equivalent proxy route is set up in vite.config.ts's `server.proxy`.
+    tunnel: '/sentry-tunnel',
   });
 }