webpack warning since 7.5.0

[Netail]

We seem to be getting the follow error since 7.5.0 with pnpm;

../../node_modules/.pnpm/require-in-the-middle@7.5.2/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.2/node_modules/require-in-the-middle/index.js
../../node_modules/.pnpm/@opentelemetry+instrumentation@0.203.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/instrumentation.js
../../node_modules/.pnpm/@opentelemetry+instrumentation@0.203.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/index.js
../../node_modules/.pnpm/@opentelemetry+instrumentation@0.203.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/index.js
../../node_modules/.pnpm/@opentelemetry+instrumentation@0.203.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/index.js

[timfish]

We seem to be getting the follow error

When are you getting this error? Install time? Bundle time? Run time?

[Netail]

We seem to be getting the follow error

When are you getting this error? Install time? Bundle time? Run time?

We seem to be getting the error when bundling a nextjs app

[timfish]

This is a webpack warning that is caused by the way Open Telemetry works. It should not stop your bundling from completing and might not even impact usage.

[Netail]

Indeed doesn't hinder bundling nor impact on usage. But can be quite misleading when you see this error. Is this something to be fixed in Open Telemetry?

[Netail]

Seems to occur since; 4b84fde (v7.5.0)

[timfish]

Is this something to be fixed in Open Telemetry?

Actually, I might be wrong assuming this is an otel issue. It's hard to tell without line numbers in the error stack!

The only slightly questionable usage of require is this library is this line but I don't agree that the require function is used in a way in which dependencies cannot be statically extracted:

require-in-the-middle/index.js

Line 156 in f7b7853

console.error('Please report this error as an issue related to Node.js %s at %s', process.version, require('./package.json').bugs.url)

[timfish]

Seems to occur since; 4b84fde (v7.5.0)

Ah, in that case it is probably caused by:

if (require.resolve.paths) {
  resolve = function (moduleName, basedir) {
    return require.resolve(moduleName, { paths: [basedir] })
  }
} 

[timfish]

If we can get #104 merged we can probably remove the code that is causing this webpack warning

[Netail]

If we can get #104 merged we can probably remove the code that is causing this webpack warning

That would be lovely, thanks :)

[Netail]

Hi @timfish ,
With version 8.0.1, I am still seeing the issue.

  ../../node_modules/.pnpm/require-in-the-middle@8.0.1/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@8.0.1/node_modules/require-in-the-middle/index.js
  ../../node_modules/.pnpm/@opentelemetry+instrumentation@0.207.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/instrumentation.js
  ../../node_modules/.pnpm/@opentelemetry+instrumentation@0.207.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node/index.js
  ../../node_modules/.pnpm/@opentelemetry+instrumentation@0.207.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/index.js
  ../../node_modules/.pnpm/@opentelemetry+instrumentation@0.207.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/index.js