workerize-loader
workerize-loader copied to clipboard
developit
🏗️ Automatically move a module into a Web Worker (Webpack loader)
Currently there is no way to pass plugins to workerize-loader. Webpack's documentation is _wrong_ when it states that child compilers inherit all hooks and plugins from the parent compiler. They...
It appears like `workerize-loader` only supports moving [export declarations](https://github.com/developit/workerize-loader/blob/master/src/index.js#L52) in the target module into a worker. I'm attempting to use it with [Bucklescript](https://bucklescript.github.io/), which compiles modules down to an export...
Awesome library! I've just found an edge case when workerizing a module that depends on a webpack external. In my webpack config i have: ```javascript module.exports = { // ......
I'm trying to use this library with Babel and TypeScript, but I'm getting a weird error. ```ts // queue.worker.ts import { TrackData } from "modules/track/types" import { shuffleArray } from...
I came to `workerize-loader` for ease-of-use, but now I wonder about about pooling-type issues imposed by my present need for overlapping tasks. So, I hope this is a helpful suggestion:...
Seems commonjs modules are not supported? ```js module.exports.xxx = function () { return 1 } ``` or ```js exports.xxx = () => { ... } ``` Is there a reason...
It seems like after I start the Gatsby dev server a second time — and webpack has a cache — the worker doesn't load with the exported worker functions set...
Used to be the case with Webpack 4 that we could pass `[path][name].[contenthash]` as the name template for workerize-loader to use; and we'd get workers output into a folder structure...
Hi! When using inline option in the config, I found duplicate worker code in my bundle. Perhaps this is because of incorrect use of `createObjectURL` and `revokeObjectURL` in the case...
