A type-safe library for communicating between JS processes, workers, or other message-passing boundaries.
No description provided.
Seamless REST/GraphQL API mocking library for browser and Node.js.
Consistent Web Workers in browser and Node.
Utilities for executing code in Web Workers
Launch latest Chrome with the Devtools Protocol port open
A fast, efficient Node.js Worker Thread Pool implementation
The worker which is used by the worker-timers package.
Temporal.io SDK Worker sub-package
worker loader module for webpack
Launch latest Edge with the Devtools Protocol port open
Communicate with a Web Worker using Promises, allowing transferList
Distribute processing tasks to child processes with an über-simple API and baked-in durability & custom concurrency options.
A little factory function to create a JSON-RPC based Web Worker implementation.
The broker which is used by the worker-timers package.
Client Server RPC worker for CSpell.
Consistent Web Workers in browser and Node.
A simple RPC layer for communicating with web workers and over other transports
A Node.js communication port that can pass messages synchronously between workers
A minimal and tiny Node.js Worker Thread Pool implementation, a fork of piscina, but with fewer features
express middleware for launching editor
A high-performance pure-javascript SHA1 implementation suitable for large binary data.
A replacement for setInterval() and setTimeout() which works in unfocused windows.
launch a web worker that can require() in the browser with browserify and webpack
Launch Resque workers from config via God. Worker`s settings are stored in the config file.
Launches a Kubernetes Job when a Resque Job is enqueued, then terminates the worker when there are no more jobs in the queue.
When used with EXEL (https://github.com/47colborne/exel), the async command will launch a Sidekiq worker
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.