Attempted import error: 'prismaIntegration' is not exported from '@sentry/nextjs' (imported as 'prismaIntegration').

[matheusrocha89]

Hi everyone,
I have a nextjs app and I am using prisma and sentry. I was following the documentation for prisma integration on sentry but when I try to add the prismaIntegration() on sentry.server.config.ts I am getting this error and the app breaks:

⚠ ./sentry.server.config.ts
Attempted import error: 'prismaIntegration' is not exported from '@sentry/nextjs' (imported as 'prismaIntegration').

Import trace for requested module:
./sentry.server.config.ts

Someone knows what is going on? Or somebody already put the prisma integration with sentry working?

[lforst]

what version of the SDK are you on?

[lforst]

To me it looks like you're importing sentry.server.config.ts from somewhere that actually runs on the client. The prismaIntegration is not available on the client.

[matheusrocha89]

Sure, I will share here:
instrumentation.ts

import * as Sentry from "@sentry/nextjs";

export async function register() {
  if (process.env.NEXT_RUNTIME === "nodejs") {
    await import("../sentry.server.config");
  }

  if (process.env.NEXT_RUNTIME === "edge") {
    console.warn("Running on EDGE?");
    await import("../sentry.server.config");
  }
}

export const onRequestError = Sentry.captureRequestError;

sentry.client.config.ts

import * as Sentry from "@sentry/nextjs";

const sentryDSN =
  process.env.NODE_ENV === "production" ? process.env.SENTRY_DSN_PROD : process.env.SENTRY_DSN_DEV;

Sentry.init({
  dsn: sentryDSN,

  // Add optional integrations for additional features
  integrations: [Sentry.replayIntegration()],

  // Define how likely traces are sampled. Adjust this value in production, or use tracesSampler for greater control.
  tracesSampleRate: !!process.env.FORCE_SENTRY ? 1 : 0.75,

  // Define how likely Replay events are sampled.
  replaysSessionSampleRate: 0.05,

  // Define how likely Replay events are sampled when an error occurs.
  replaysOnErrorSampleRate: 0.33,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,

  enabled: process.env.NODE_ENV === "production" || !!process.env.FORCE_SENTRY,
});

sentry.server.config.ts

import * as Sentry from "@sentry/nextjs";
import { PrismaInstrumentation } from "@prisma/instrumentation";

const sentryDNS =
  process.env.NODE_ENV === "production" ? process.env.SENTRY_DSN_PROD : process.env.SENTRY_DSN_DEV;

Sentry.init({
  dsn: sentryDNS,

  // Define how likely traces are sampled. Adjust this value in production, or use tracesSampler for greater control.
  tracesSampleRate: !!process.env.FORCE_SENTRY ? 1 : 0.75,
  integrations: [
    Sentry.prismaIntegration({
      prismaInstrumentation: new PrismaInstrumentation(),
    }),
  ],

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,

  sendDefaultPii: true,
  beforeSend(event) {
    if (event.request && event.request.headers) {
      delete event.request.headers["authorization"];
      delete event.request.headers["cookie"];
    }
    return event;
  },

  enabled: process.env.NODE_ENV === "production" || !!process.env.FORCE_SENTRY,
});

[matheusrocha89]

The print screen on the first message opening the issue was when I was already trying to update the prisma to version 6 too so I could solve the issue. But even though the same error appeared, I rolled back everything to the current version (Prisma 5 and Sentry 9.2.0) and followed the documentation on the Sentry page.

[lforst]

This is very odd. If you find the time to upload a repro I can pull I can take a look, but other than that I wouldn't know what the issue here is.

[matheusrocha89]

@lforst Ok, I will take the time today to do that. I didn't try with a clean nextjs project, maybe I will find out something wrong with my project or not, in both cases I will update you here.