Require.context not working after installing sentry on Next.js project

[dorianw123]

Environment

SaaS (https://sentry.io/)

Version

No response

Link

No response

DSN

No response

Steps to Reproduce

I've installed sentry on my Next.js project. I'm trying to use require.context like so:

const flagImages = importAll(
  require.context("../../public/images/flags", false, /\.(png|jpe?g|svg)$/)
);

This was working fine before installing sentry, but doesn't work after installing sentry. I assume the reason it no longer works is because sentry changes the webpack configuration.

I tried using import.meta.webpackContext as the ESM alternative to require.context, but this didn't work either - I just get import.meta.webpackContext is undefined.

Expected Result

Should be able to use require.context or import.meta.webpackContext

Actual Result

[getsantry]

Assigning to @getsentry/support for routing, due by Monday, January 30th at 10:47 am (yyz). ⏲️

[getsantry]

Routing to @getsentry/team-web-sdk-frontend for triage, due by Tuesday, January 31st at 11:07 am (sfo). ⏲️

[lforst]

Thanks for reporting this. We'll look into it!

[joshuajaco]

This can be traced back to the same underlying issue as #6943. rollup-plugin-commonjs trying to convert commonjs to esm

[lforst]

Hi, we just released an update that should fix this problem. https://github.com/getsentry/sentry-javascript/releases/tag/7.35.0

Let me know if upgrading the SDK fixes this issue for you!