web-worker

Consistent Web Workers in browser and Node.

by developit

Star on GitHub ForkWebsite npm

JavaScript

1.2k stars 58 forks 13 contributorsQuiet · 1y agoSince 2019 1.5.0Apache-2.0

Meet the team

See all 13 on GitHub →

developit63 contributions

martines300018 contributions

guybedford4 contributions

eshaz2 contributions

Jarred-Sumner2 contributions

mmomtchev2 contributions

pubkey2 contributions

phated1 contribution

Languages

View on GitHub →

JavaScript98.9%

TypeScript1.1%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

3 of 6 standards met

Community profile →

✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 6 in progress · Last activity 1y ago

See all on GitHub →

Blob URL does not work on Node.jsOpenIssue

The readme says: Worker() accepts a module URL, Blob URL or Data URL But running the following on Node.js 18 results in a crash:

sindresorhus · 6d ago

fix: allow importing inside a NodeJS worker with no workerDataOpenPR

This PR fixes #57 I added a to the destructuring to ensure we have a valid value to destructure. In addition to that I added a new attribute with a unique name (includes a UUID, so it's basically impossible to set this by accident) to the . This ensures we can reliably verify that we are running in a worker thread, which was created by . All other threads will use the code path (and not the code path). Something similar was already suggested by eshaz in #40: [...] One enhancement might be to randomize the property name. This change assumes that a parent thread won't send a property in the ...

DerZade · 3w ago

`1.5.0` regression: workers treated as ESM by defaultOpenIssue

Hi, Glad to stumbled on this neat project and looking forward to using it to write more consistent browser-node code. I'm trying to get duckdb-wasm working in node, I found a example in their repo. It fails when I run it, with error: It uses web-worker, and it seems like the worker code (clearly CJS and with file extension ) gets detected like an ESM module. Downgrading web-worker from to fixes the issue. I tried a few other things like passing type: commonjs, type: classic - none worked. Suggests a regression in 1.5.0 release (edit: unless changing the default behavior in 1.5.0 is intentional) Thanks Declan

declann · 1mo ago

Recent fixes

View closed PRs →

How to stop a worker?ClosedIssue

[Please ignore]

ecofi · 1y ago

Warning: "Critical dependency: the request of a dependency is an expression"ClosedIssue

Using latest nextjs, I'm getting Seems related to #6 looks similiar to https://github.com/iamakulov/moment-locales-webpack-plugin/issues/43 I'm not yet knowledgable enough about ESM modules and their handling, but will hop by to report if I manage to solve this. Cheerio

wildeyes · 1y ago

Structured data for AI agents

Repository: developit/web-worker. Description: Consistent Web Workers in browser and Node. Stars: 1175, Forks: 58. Primary language: JavaScript. Languages: JavaScript (98.9%), TypeScript (1.1%). License: Apache-2.0. Homepage: https://npm.im/web-worker Latest release: 1.5.0 (1y ago). Open PRs: 6, open issues: 11. Last activity: 1y ago. Community health: 57%. Top contributors: developit, martines3000, guybedford, eshaz, Jarred-Sumner, mmomtchev, pubkey, phated, danielroe, pankdm and others.