reporting errors to sentry

turns out that hardcoding the SENTRY_DSN was the necessary change. idk
why though. the sentry docs, referenced below, mention using the env
variable.

https://docs.sentry.io/product/sentry-basics/concepts/dsn-explainer/#what-the-dsn-does

Author: alishaevn

sentry.client.config.js

@@ -5,7 +5,7 @@
 import * as Sentry from '@sentry/nextjs'
 
 Sentry.init({
-  dsn: process.env.SENTRY_DSN,
+  dsn: 'https://[email protected]/4504810271408128',
   // Adjust this value in production, or use tracesSampler for greater control
   // ref: https://develop.sentry.dev/sdk/performance/#sdk-configuration
   tracesSampleRate: 1.0,

sentry.edge.config.js

@@ -5,7 +5,7 @@
 import * as Sentry from '@sentry/nextjs'
 
 Sentry.init({
-  dsn: process.env.SENTRY_DSN,
+  dsn: 'https://[email protected]/4504810271408128',
   // Adjust this value in production, or use tracesSampler for greater control
   // ref: https://develop.sentry.dev/sdk/performance/#sdk-configuration
   tracesSampleRate: 1.0,

sentry.server.config.js

@@ -5,7 +5,7 @@
 import * as Sentry from '@sentry/nextjs'
 
 Sentry.init({
-  dsn: process.env.SENTRY_DSN,
+  dsn: 'https://[email protected]/4504810271408128',
   // Adjust this value in production, or use tracesSampler for greater control
   // ref: https://develop.sentry.dev/sdk/performance/#sdk-configuration
   tracesSampleRate: 1.0,

utils/api/base.js

@@ -10,13 +10,7 @@ export const fetcher = (url, token) => {
   return api.get(url, { headers: `Bearer 1234` })
     .then(res => res.data)
     .catch(error => {
-      console.log({ error })
-      Sentry.captureException(new Error(error))
-      // Sentry.captureEvent({
-      //   message: error,
-      //   stacktrace: error.stacktrace,
-      //   name: error.name,
-      // })
+      Sentry.captureException(error)
     })
 }