Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Warning (workerize-loader): output.globalObject is set to "window". It should be set to "self" or "this" to support HMR in Workers
See original GitHub issueHeya,
I’m trying to follow up your initial work in https://github.com/angular/angular-cli/pull/12575.
I see Warning (workerize-loader): output.globalObject is set to "window". It should be set to "self" or "this" to support HMR in Workers when serving, but not when building.
That warning seems to come from here: https://github.com/GoogleChromeLabs/worker-plugin/blob/cb00d315157412c405f9441bd7ff7662e6c16eb9/src/loader.js#L33
What’s the intended way of addressing this warning? I’d like to keep the globalObject settings of the main compilation unaltered.
As a side-note, the name workerize-loader is misleading. It took me a while to figure out that it came from this package since I was looking for a workerize-loader in node modules.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hm yes, that would make sense. Regardless, thank you for the swift reply, will update 👍
There’s something I don’t quite understand though. If the child compiler already uses the right globalObject, why does it matter what globalObject the parent uses?