bump next to 12.1.0

lib/helpers/fetcher.ts

@@ -0,0 +1,7 @@
+// very simple fetch wrapper that's passed into SWR hooks:
+// https://swr.vercel.app/docs/data-fetching#fetch
+// note: fetch does *not* need to be poly/ponyfilled in Next.js:
+// https://nextjs.org/blog/next-9-1-7#new-built-in-polyfills-fetch-url-and-objectassign
+
+// eslint-disable-next-line no-undef
+export const fetcher = (url: RequestInfo) => fetch(url).then((res) => res.json());

lib/helpers/sentry.ts

@@ -0,0 +1,31 @@
+import * as Sentry from "@sentry/node";
+// eslint-disable-next-line @typescript-eslint/no-unused-vars
+import * as Tracing from "@sentry/tracing";
+
+// https://docs.sentry.io/platforms/node/configuration/options/
+Sentry.init({
+  dsn: process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN || "",
+  environment: process.env.NODE_ENV || process.env.VERCEL_ENV || process.env.NEXT_PUBLIC_VERCEL_ENV || "",
+  tracesSampleRate: 1.0,
+});
+
+export const logServerError = async (error: string | Error) => {
+  try {
+    // log error to sentry
+    Sentry.captureException(error);
+    // give it 2 seconds to finish sending:
+    // https://docs.sentry.io/platforms/node/configuration/draining/
+    await Sentry.flush(2000);
+  } catch (sentryError) {
+    // cue inception bong
+    console.error("Encountered an error logging an error... We are doomed.", sentryError);
+  }
+
+  // also log the error normally to the Vercel console; will get picked up by log drain
+  console.error(error);
+
+  // we really don't want to return *any* error from logging an error, so just keep it on the dl
+  return true;
+};
+
+export default Sentry;