Module not found: Can't resolve '_http_common'

[kettanaito]

Link to the code that reproduces this issue

mswjs/msw#2291

To Reproduce

Please follow the reproduction steps in the linked issue above.

Current vs. Expected behavior

Current

Next.js throws an error, unable to import a built-in _http_common module in Node.js.

Expectd

Next.js properly imports the built-in module.

Provide environment information

Irrelevant, this is a webpack configuration issue.

Which area(s) are affected? (Select all that apply)

Developer Experience, Runtime, Webpack

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed)

Additional context

I believe this is caused by the Next's default webpack config not listing _http_common in config.externals.

Any thoughts on listing all built-in Node.js modules as external?

{
  // All built-in modules in Node.js must be treated as external.
  externals: require('module').builtinModules
}

I'm proposing this because contributors report that adding _http_common into config.externals helps them. This should be handled on Next's side.