Critical dependency warning with require-in-the-middle after upgrading to Sentry 8.52.0 in Next.js app

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?

@sentry/nextjs

SDK Version

8.52.0

Framework Version

React 19.0.0 & Next.js 15.1.6

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Create a Next.js application
Install latest @sentry/nextjs (8.52.0)
Run the development server
Observe the critical dependency warning

Expected Result

No critical dependency warnings during development server startup.

Actual Result

 ⚠ ./node_modules/.pnpm/require-in-the-middle@7.5.0/node_modules/require-in-the-middle/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

Import trace for requested module:
./node_modules/.pnpm/require-in-the-middle@7.5.0/node_modules/require-in-the-middle/index.js
./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/instrumentation.js
./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/index.js
./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/index.js
./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/index.js
./node_modules/.pnpm/@sentry+opentelemetry@8.52.0_@opentelemetry+api@1.9.0_@opentelemetry+core@1.30.1_@opentelemet_usgluomwp3va5k3mad5pbwdxfm/node_modules/@sentry/opentelemetry/build/cjs/index.js
./node_modules/.pnpm/@sentry+nextjs@8.52.0_@opentelemetry+core@1.30.1_@opentelemetry+api@1.9.0__@opentelemetry+ins_fvm7vkuyikfkbj6gbt6uu4g4sq/node_modules/@sentry/nextjs/build/cjs/server/index.js
./node_modules/.pnpm/@sentry+nextjs@8.52.0_@opentelemetry+core@1.30.1_@opentelemetry+api@1.9.0__@opentelemetry+ins_fvm7vkuyikfkbj6gbt6uu4g4sq/node_modules/@sentry/nextjs/build/cjs/index.server.js

Hi, we'll resolve this warning with the next release!

@lforst

Awesome, thanks @lforst!

@lforst

Hi @lforst,

Since upgrading to @sentry/nextjs@8.52.0, I’m encountering the same "require-in-the-middle" Critical Dependency Warning in Next.js. I saw that you mentioned a fix is planned for the next release.

For the interim solution, could you clarify: 1️⃣ Which is the latest stable release that does not have this issue? Should we downgrade to @sentry/nextjs@8.51.0, or is there a better version? 2️⃣ Would you recommend suppressing the warning using "ignoreWarnings" in next.config.js, or is downgrading a better approach? 3️⃣ What’s the estimated timeline for the fix in the next release?

Thanks in advance for your help! (cc: @getsantry @danielkoller)

Never mind - my issue was related to my usage of withSentryConfig. Fixed that up and I'm not getting the warning anymore.

Never mind - my issue was related to my usage of withSentryConfig. Fixed that up and I'm not getting the warning anymore.

How did you fix it?

@haydnjm

Never mind - my issue was related to my usage of withSentryConfig. Fixed that up and I'm not getting the warning anymore.

~~@haydnjm Can you clarify how you fixed it? I'm getting the same error right now as well~~

Error: Cannot find module 'require-in-the-middle'
Require stack:
- /var/task/packages/service/.next/server/app/page.js
- /var/task/node_modules/.pnpm/next@14.2.28_@babel+core@7.26.10_@opentelemetry+api@1.9.0_@playwright+test@1.52.0_react-dom@1_lgmiccyhb4drfv4bvfqhftpu5e/node_modules/next/dist/compiled/next-server/server.runtime.prod.js
- /var/task/packages/service/___next_launcher.cjs
- /opt/rust/nodejs.js

Update: Just following up on this the errors in the development console can be fixed through configuring the next.config.js file

next.config.js

...
 webpack: (config) => {
    config.externals = config.externals || [];
    config.externals.push("require-in-the-middle");
    return config;
  }
...

I also installed require-in-the-middle as a devDepenency and it seemed to solve the issue in both our e2e tests and CI/CD pipeline

package.json

  "devDependencies": {
...
    "require-in-the-middle": "^7.5.2",
...
  },

If you still encounter this issue please review the troubleshooting steps in our documentation or check this issue history for additional solutions and workarounds.

Navigation Menu

Repository navigation

Critical dependency warning with require-in-the-middle after upgrading to Sentry 8.52.0 in Next.js app #15209

Is there an existing issue for this?

How do you use Sentry?

Which SDK are you using?

SDK Version

Framework Version

Link to Sentry event

Reproduction Example/SDK Setup

Steps to Reproduce

Expected Result

Actual Result

102 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Critical dependency warning with require-in-the-middle after upgrading to Sentry 8.52.0 in Next.js app #15209

Description

Is there an existing issue for this?

How do you use Sentry?

Which SDK are you using?

SDK Version

Framework Version

Link to Sentry event

Reproduction Example/SDK Setup

Steps to Reproduce

Expected Result

Actual Result

Activity

lforst commented on Jan 29, 2025

danielkoller commented on Jan 29, 2025

sousounibajis commented on Jan 30, 2025

102 remaining items

haydnjm commented on May 5, 2025

tkodev commented on May 8, 2025

chaodonghu commented on May 8, 2025

chargome commented on May 14, 2025

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions