Jason Miller

Hiya - this is correct, since Greenlet workers do not have an origin. Even if IndexedDB was accessible from the greenlet function context, it would be a different database than...

Yes - workerize only recognizes ES Modules. I'm open to changing that, making the export detection work at runtime instead. It will require making module instantiation asynchronous though.

Sorry for the late reply. In order to know what's going on, I'd need to know if you're enabling Workerize-loader using inline loader syntax, or via module.rules mappings in your...

Released in [0.3.0](https://github.com/developit/jsdom-worker/releases/tag/0.3.0), sorry for ignoring this.

> ### Note for folks finding this: this is a proposal, `inline` doesn't yet exist This isn't because of CORS, but rather because sites like google.com tend to disallow all...

For the folks commenting about `inline` not working - I was proposing that feature, it is not something WorkerPlugin currently implements. Building transparent Blob/inline support is likely possible, but in...

@alangdm try this version: ```js function Worker(url, opts) { var blob = new Blob(['importScripts('+JSON.stringify(url)+')'], { type: 'text/javascript' }); return self.Worker(URL.createObjectURL(blob), opts); } new Worker("./my-worker.js", { type: "module" }); ``` The...

FWIW I'd be open to adding an option to worker-plugin that outputs the shimmed code. Better yet, an option to specify "here's how to get the Worker constructor", like: ```js...

Bundling a worker to a data URI is generally not a good idea. It's putting extra strain on the parser in the main thread for no reason. I'm not sure...

@sjsakib it's strange that you would be getting an ESLint error on generated output. Gatsby needs to configure react-hot-loader to only be applied to the main Compilation. It appears they...