[Next.js] Figure out a way to silence the import/require-in-the-middle warnings for Turbopack

[lforst]

Description

Seems like Turbopack is more strict in what it will do when there would be 2 different versions of a package it could bundle. Currently it will refuse to build (?). Maybe we can iron out the kinks here.

 ⚠ ./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package import-in-the-middle can't be external
The request import-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install import-in-the-middle from the project directory.

[benjick]

Can these be ignored?

[timfish]

Which warnings are these and what do they look like? Do these warnings still exist now that in v9 we use import-in-the-middle in a mode where it doesn't attempt to instrument everything?

[benjick]

These are the ones I get:

 ○ Compiling /login ...
 ✓ Compiled /login in 1488ms
 ⚠ ./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package import-in-the-middle can't be external
The request import-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install import-in-the-middle from the project directory.


 ⚠ ./node_modules/.pnpm/@opentelemetry+instrumentation@0.57.1_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package import-in-the-middle can't be external
The request import-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install import-in-the-middle from the project directory.


 ⚠ ./node_modules/.pnpm/@sentry+node@9.1.0/node_modules/@sentry/node/build/cjs/sdk
Package import-in-the-middle can't be external
The request import-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install import-in-the-middle from the project directory.


 ⚠ ./node_modules/.pnpm/@opentelemetry+instrumentation@0.56.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package require-in-the-middle can't be external
The request require-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install require-in-the-middle from the project directory.


 ⚠ ./node_modules/.pnpm/@opentelemetry+instrumentation@0.57.1_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package require-in-the-middle can't be external
The request require-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install require-in-the-middle from the project directory.

• next@15.1.7
• @sentry/nextjs@9.1.0

[novelnet]

having same issues, two different versions of import-in-the-middle in @sentry/node@9.8.0 causing the warnings
⚠ ./node_modules/@opentelemetry/instrumentation/build/esm/platform/node Package import-in-the-middle can't be external The request import-in-the-middle matches serverExternalPackages (or the default list). The package resolves to a different version when requested from the project directory (1.13.1) compared to the package requested from the importing module (1.11.2). Make sure to install the same version of the package in both locations.

[lforst]

@novelnet Yes, this is fixed by adding an override to your package manager to install one specific version. In the case of import-in-the-middle, the later version is usually the better choice.

[novelnet]

@lforst thank you, but means to keep track on all sentry updates which may change package versions. Would be nice to fix this on sentry's side

[lforst]

This is not 100% fixable on our side. We are not in control of other dependencies and what they install.

[MonstraG]

What should we do with the OP's case? (Not the version mismatch).

[lforst]

@MonstraG maybe what the error message suggests?

Try to install it into the project directory by running npm install import-in-the-middle from the project directory.