GitShow/developit/workerize-loader
developit

workerize-loader

๐Ÿ—๏ธ Automatically move a module into a Web Worker (Webpack loader)

by developit
web-workerwebpackwebpack-loaderwebpack-pluginworker
Star on GitHubForkWebsitenpm

JavaScript

2.3k stars85 forks17 contributorsQuiet ยท 4y agoSince 20182.0.0

Meet the team

See all 17 on GitHub โ†’
developit
developit80 contributions
jaikme
jaikme4 contributions
greenkeeper[bot]Bot
greenkeeper[bot]4 contributions
yellott
yellott3 contributions
QingWei-Li
QingWei-Li2 contributions
dpraimeyuu
dpraimeyuu1 contribution
danielbayerlein
danielbayerlein1 contribution
danieldunderfelt
danieldunderfelt1 contribution

Languages

View on GitHub โ†’
JavaScript100%

Commit activity

Last 12 weeks ยท 0 commits

Full graph โ†’

Community health

1 of 6 standards met

Community profile โ†’
28
โœ“READMEโ—‹Licenseโ—‹Contributingโ—‹Code of Conductโ—‹Issue Templateโ—‹PR Template

Recent PRs & issues

Quiet ยท Last activity 4y ago
See all on GitHub โ†’
gersomvg
Breaks on latest gatsby, only when there is a webpack cacheOpenIssue

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 on the object. The moment I clear webpack's cache and restart the dev server, the worker loads fine again. Does this very limited description by any chance give you a quick insight about what might be causing this? I'm afraid I can't really give more details, because the inner workings of gatsby/webpack is just one big black box to me. I can of course make a minimal reproduction with a newly bootstrapped gatsby, if this would be of any help?

gersomvg ยท 1y ago
chris-aeviator
FetchCompileWasmTemplatePlugin is not a constructorOpenIssue

I'm running into this in my react app (next.js) when trying to use the

chris-aeviator ยท 3y ago

Recent fixes

View closed PRs โ†’
kpdecker
Support webpack 5MergedPR

Expands on/supersedes #100. Removing the parser logic simplifies the webpack API integration and number of points that break as a result of webpack 5 changes. Note that karma-webpack would not play nicely when I installed webpack 5, so while this appears to compile correctly, it has not been tested at runtime with Webpack 5. Possible fix for #77

kpdecker ยท 1mo ago
kpdecker
Add support for imported exportsMergedPR

Adds support for field appears to be around for all of Webpack 4. If prior webpacks are supported still, then will need a simple adapter layer. Approached this in additive fashion to reduce the risk of this PR. I do have a stash locally that replaces the custom traversal logic glad to include that in this PR if desired. Mostly deletes the custom parser hooks. Fixes #15

kpdecker ยท 1mo ago
kpdecker
Pass additional error props on RPC busMergedPR

Allows access to metadata the may have been applied to these errors.

kpdecker ยท 1mo ago
Structured data for AI agents

Repository: developit/workerize-loader. Description: ๐Ÿ—๏ธ Automatically move a module into a Web Worker (Webpack loader) Stars: 2306, Forks: 85. Primary language: JavaScript. Languages: JavaScript (100%). Homepage: https://npm.im/workerize-loader Topics: web-worker, webpack, webpack-loader, webpack-plugin, worker. Latest release: 2.0.0 (4y ago). Open PRs: 3, open issues: 22. Last activity: 4y ago. Community health: 28%. Top contributors: developit, jaikme, greenkeeper[bot], yellott, QingWei-Li, dpraimeyuu, danielbayerlein, danieldunderfelt, wellcaffeinated, kenrick95 and others.

ยท@ofershap

Replace github.com with gitshow.dev