Attempted import error: 'wrapGetServerSidePropsWithSentry' is not exported from '@sentry/nextjs'

[mcmxcdev]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using? If you use the CDN bundles, please specify the exact bundle (e.g. bundle.tracing.min.js) in your SDK setup.

@sentry/nextjs

SDK Version

7.38.0

Framework Version

React 18.2.0

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

No idea

Expected Result

No warning to pop up. It seems though that it doesn't break anything.

Actual Result

> nx run app:build:production

info  - Skipping validation of types
info  - Skipping linting
info  - Creating an optimized production build  
warn  - Compiled with warnings

../../libs/shared/utils/src/lib/session.ts
Attempted import error: 'wrapGetServerSidePropsWithSentry' is not exported from '@sentry/nextjs' (imported as 'wrapGetServerSidePropsWithSentry').

[lforst]

Thanks for writing in, I pushed a fix: #7256

[jvidalv]

I'm still experiencing this with latest version (7.39.0):

And this goes on for every page in the site.

The latest version that works (tested all of them) is this one 7.31.1.

We are using pnpm and pnpm workspaces.

[lforst]

@jvidalv It is super unlikely that this is still happening in the new version. Can you clear your pnpm cache and try again?

[jvidalv]

Hi @lforst , thanks for the quick reply.

I did indeed use: pnpm store prune, and also deleted node_modules and then I did run it again (prune). It didn't fix the issue that I shared.

As mentioned the latest version that seems to work is 7.31.1.

[lforst]

@jvidalv got it. Can you share a reproduction example? Just something we can clone or a https://stackblitz.com/ would be enough.

[jvidalv]

@lforst finally found the root cause of the error, any page that has:

export const config = {
  runtime: 'experimental-edge'
}

Configured, makes the build fail with versions bigger that 4.31 with the error that I shared.

[lforst]

@jvidalv woah didn't even know you could do that. Would you mind creating a separate issue for this so we can fix it? Thanks!

[jvidalv]

#7522

[lforst]

Thank you!