Bug report
I have code like this:
new Worker(import.meta.url)
where module spawns itself as a Worker when multithreading is enabled.
What is the current behavior?
Webpack transforms import.meta.url into a file: URI, which fails to get spawned in runtime.
What is the expected behavior?
Handling of
new Worker(import.meta.url)
should be equivalent to
new Worker(new URL('explicit-own-filename.js', import.meta.url))
which Webpack already supports.
Other relevant information:
webpack version: 5.20.1
Bug report
I have code like this:
where module spawns itself as a Worker when multithreading is enabled.
What is the current behavior?
Webpack transforms
import.meta.urlinto afile:URI, which fails to get spawned in runtime.What is the expected behavior?
Handling of
should be equivalent to
which Webpack already supports.
Other relevant information:
webpack version: 5.20.1