-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new Worker(import.meta.url)
doesn't work as expected
#12638
Comments
script tag must be support ESM. |
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. |
Still valid |
Having thought about this a bit more, while I think it would be useful, it's likely not the most uncommon usecase and other bundlers don't seem to support this either. To keep consistency I suppose I'll close it. |
@RReverser I think we can keep open, for me it is feature/enhancement than bug |
FYI I just implemented support for this in Parcel (see link above). Came across this issue while I was researching so thought I would let you know. 😉 |
Ah thanks :) |
Issue was closed because of inactivity. If you think this is still a valid issue, please file a new issue with additional information. |
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.url
into 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
The text was updated successfully, but these errors were encountered: