Adding Sentry is basically done now. We have a nice lil component to help us get started to!

scripts/next.config.default.js

@@ -3,6 +3,7 @@
  * for Docker builds.
  */
 import './src/env.js';
+import { withSentryConfig } from '@sentry/nextjs';
 
 /** @type {import("next").NextConfig} */
 const config = {
@@ -15,11 +16,46 @@ const config = {
       },
     ],
   },
+  serverExternalPackages: ['require-in-the-middle'],
   experimental: {
     serverActions: {
       bodySizeLimit: '10mb',
     },
   },
+  //turbopack: {
+  //rules: {
+  //'*.svg': {
+  //loaders: ['@svgr/webpack'],
+  //as: '*.js',
+  //},
+  //},
+  //},
 };
 
-export default config;
+const sentryConfig = {
+  // For all available options, see:
+  // https://www.npmjs.com/package/@sentry/webpack-plugin#options
+  org: 'gib',
+  project: 't3-supabase-template',
+  sentryUrl: process.env.SENTRY_URL,
+  authToken: process.env.SENTRY_AUTH_TOKEN,
+  // Only print logs for uploading source maps in CI
+  silent: !process.env.CI,
+  // For all available options, see:
+  // https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/
+  // Upload a larger set of source maps for prettier stack traces (increases build time)
+  widenClientFileUpload: true,
+  // Route browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers.
+  // This can increase your server load as well as your hosting bill.
+  // Note: Check that the configured route will not match with your Next.js middleware, otherwise reporting of client-
+  // side errors will fail.
+  tunnelRoute: '/monitoring',
+  // Automatically tree-shake Sentry logger statements to reduce bundle size
+  disableLogger: true,
+  // Capture React Component Names
+  reactComponentAnnotation: {
+    enabled: true,
+  },
+};
+
+export default withSentryConfig(config, sentryConfig);