task queue to process tesk one by one
Gulp non-dependent ordered tasks runner. It solves the issue with the run-sequence module that doesn't abort the task chain on error.
micromark extension to support GFM task list items
mdast extension to parse and serialize GFM task list items
Chain functions, generators, Node streams, and Web streams into a pipeline with backpressure support.
HANDLE CONFIGURATION ONCE AND FOR ALL
A utility for managing a prototype chain
Distributed task scheduler and rate limiter
A shim for the setImmediate efficient script yielding API
Coinbase Design System - MCP Server
API for combining call site modifiers
A simple tool to keep requests to be executed in order.
TypeScript definitions for stream-chain
High-priority task queue for Node.js and browsers
task list extension for tiptap
task item extension for tiptap
A simple asynchronous tool
High-priority task queue for Node.js and browsers
MediaPipe Vision Tasks
The Aikido Safe Chain wraps around the [npm cli](https://github.com/npm/cli), [npx](https://github.com/npm/cli/blob/latest/docs/content/commands/npx.md), [yarn](https://yarnpkg.com/), [pnpm](https://pnpm.io/), [pnpx](https://pnpm.io/cli/dlx), [rush](https
A markdown-it plugin to create GitHub-style task lists
A fast, efficient Node.js Worker Thread Pool implementation
No description provided.
[](https://www.npmjs.com/package/async-queue-chain) [](https://bundlephobia.com/r
Evaluates JSON-based rules against task payloads with 18+ operators, structured explanations, and standalone client support
Template-based payload transformation between tasks with multiple engines, schema validation, and composition
Enables accessing of invocation chain from within the task execution context
Attention, transformation, and routing with confidence scoring, pain signals, homeostasis, and self-governance
Chain together code tasks similar to Unix pipes
ace-sim executes preset-driven simulation chains across multiple providers so teams can validate ideas, review tasks, and compare synthesis outcomes before taking action.
StepSequencer is a Ruby gem providing a lightweight, intuitive DSL for defining and orchestrating a sequence of operations, also known as a workflow. Inspired by the functionality of musical sequencers, StepSequencer allows developers to chain together a series of steps that are executed in order, with the capability to halt the sequence based on custom conditions. This gem is particularly useful for scenarios where a set of tasks must be performed in a specific sequence, and where each task might depend on the outcome of the previous one.
Adds a rake task that accepts a view partial file name and outputs the render chain along with best guesses as to the routes used to render the partial.
Rum Runner is a Rake-based utility for building multi-stage Dockerfiles. Users can pair a multi-stage Dockerfile with a Rumfile that uses a Rake-like DSL to customize each stage's build options and dependencies. The `rum` executable allows users to easily invoke builds, shell-into specific stages for debugging, and export artifacts from built containers. Rum Runner has the following features: * Fully compatible with Rake * Rake-like DSL/CLI that enable simple annotation and execution of builds * Rumfiles are completely defined in standard Ruby syntax, like Rakefiles * Users can chain Docker build stages with prerequisites * Artifacts can be exported from stages * Shell tasks are automatically provided for every stage * Stage, artifact, and shell, steps can be customized
== OceanDynamo As one important use case for OceanDynamo is to facilitate the conversion of SQL databases to no-SQL DynamoDB databases, it is important that the syntax and semantics of OceanDynamo are as close as possible to those of ActiveRecord. This includes callbacks, exceptions and method chaining semantics. OceanDynamo follows this pattern closely and is of course based on ActiveModel. The attribute and persistence layer of OceanDynamo is modeled on that of ActiveRecord: there's +save+, +save!+, +create+, +update+, +update!+, +update_attributes+, +find_each+, +destroy_all+, +delete_all+, +read_attribute+, +write_attribute+ and all the other methods you're used to. The design goal is always to implement as much of the ActiveRecord interface as possible, without compromising scalability. This makes the task of switching from SQL to no-SQL much easier. OceanDynamo uses only primary indices to retrieve related table items and collections, which means it will scale without limits. OceanDynamo is fully usable as an ActiveModel and can be used by Rails controllers. Thanks to its structural similarity to ActiveRecord, OceanDynamo works with FactoryBot. See also Ocean, a Rails framework for creating highly scalable SOAs in the cloud, in which ocean-dynamo is used as a central component: http://wiki.oceanframework.net
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.