thread worker group
A streaming way to send data to a Node.js Worker Thread
Runs the following loaders in a worker pool
Use Rollup with workers and ES6 modules today.
Utilities for executing code in Web Workers
A mutex for guarding async workflows
A minimal and tiny Node.js Worker Thread Pool implementation, a fork of piscina, but with fewer features
Client Server RPC worker for CSpell.
Use Rollup with workers and ES6 modules today.
a built-in tap extension for t.worker()
Serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Type-safe, structured communication between worker threads and parent processes via TypeScript meta-programming.
Helpers for communicating between JavaScript environments using message passing.
Utilities for type-safe Web Worker communication with RPC.
Relocate resource intensive third-party scripts off of the main thread and into a web worker.
MongoDB shell runtime that lives in a worker thread
MSR JavaScript Cryptography Library
A transport for pino that sends messages to Loki
A Node.js communication port that can pass messages synchronously between workers
WASI threads proposal implementation in JavaScript
A native Node.js module that can capture JavaScript stack traces from main and worker threads, even with blocked event loops.
SQLite Wasm conveniently wrapped as an ES Module.
Web workers & worker threads as simple as a function call
A replacement for setInterval() and setTimeout() which works in unfocused windows.
This is a beanstalk-based job-queueing-manager, replacement for gem 'stalker' with additions: 1. jobs grouping 2. jobs threading and forking 3. logging 4. background run (as daemon) 5. stalker makes to include full gem in application, but needed only client-side This is a client-side gem. For a worker you need * http://github.com/GearHead90/beanworker
Enhances the ActionMailer Previews introduced in 4.1 by automatically creating ActionMailer Previews at runtime in development mode. See automatic previews of your ActionMailer emails, with no extra effort or mock data. Install the action_mailer_auto_previews gem into your :development group, and it'll 'just work' with sensible defaults. Each ActionMailer email object that has .deliver or .deliver_later called will automatically launch your default browser right to a ActionMailer Preview page with the real data passed to that email. Flexible options allow you to alter this behavior as well. Warning: Since this is dynamically creating Ruby classes/methods, you will want to make sure your web-server is single threaded. For example, if you're using Puma, be sure to set the `workers` configuration parameter to 1.