Web Workers in a project with experiments.outputModule = true call importScripts despite being loaded with {type: "module"}

[GingerIndustries]

Bug report

What is the current behavior?

In a project with experiments.outputModule = true, the following code:

// main code
new Worker(new URL("<worker path>", import.meta.url))

// worker code
import { Stuff } from "some-really-big-module-that-gets-its-own-chunk"

will generate a main file that calls new Worker("<processed URL>", { type: "module" }), but a worker that calls importScripts() to load some-really-big-module-that-gets-its-own-chunk. This results in an error when the worker is loaded.

Reproduce

A minimum viable example may be found at https://github.com/GingerIndustries/webworker-mre.

What is the expected behavior?

Workers loaded in a project under these conditions should only use ES module imports to load dependencies.

Other relevant information:
webpack version: 5.89.0
Node.js version: 18.13.0
Operating System: Debian Bookworm
Additional tools: None

[alexander-akait]

I want to say it is a feature, we don't support ES module output for workers right now

[webpack-bot]

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

[alexander-akait]

bump