git404hub

what is workq fr?

starptech/workq — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2017-11-18

JavaScriptAudience · developerComplexity · 2/5DormantSetup · easy

tl;dr

A lightweight JavaScript library that runs tasks one at a time in a guaranteed order, so job A always finishes before job B starts, even when jobs have their own nested sub-tasks.

vibe map

mindmap
  root((repo))
    What it does
      Sequential task queue
      Nested queues
      Guaranteed order
    Tech stack
      JavaScript
      Callbacks
      Async await
    Use cases
      Document pipelines
      Deployment steps
      Ordered workflows
    Audience
      Developers
    Features
      Drain hook
      Singleton queues
      Tiny library

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Build a document processing pipeline where convert, validate, and upload must happen in that exact order.

VIBE 2

Coordinate a multi-step deployment workflow that requires strict sequential execution.

VIBE 3

Run nested subtasks in order within a larger job, like validating each item in a batch before moving on.

VIBE 4

Trigger a completion action or log message once all queued work finishes using the drain hook.

what's the stack?

JavaScript

how it stacks up fr

starptech/workq3rd-eden/ircb.ioa15n/a15n
LanguageJavaScriptJavaScriptJavaScript
Last pushed2017-11-182016-11-162019-04-07
MaintenanceDormantDormantDormant
Setup difficultyeasyeasyeasy
Complexity2/52/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

in plain english

Workq is a lightweight tool that runs tasks one at a time in a predictable order, rather than all at once. Think of it like a to-do list checker that works through your tasks sequentially, it guarantees that job A finishes before job B starts. If you've ever needed something to happen in a specific sequence and didn't want to manually coordinate timing, this is what it does. The way it works is straightforward: you create a queue, add jobs to it, and they execute in order. Each job gets a callback to signal when it's done, then the next job runs. What makes this interesting is that jobs can spawn their own nested queues, imagine a task that itself has subtasks that must complete in order before moving on. The main queue starts automatically once you add your first job, and nested queues start when you tell them to inside a parent job. You might use this if you're building something like a document processing pipeline (convert, validate, upload, in that exact order), a deployment workflow with multiple sequential steps, or any scenario where you need strict ordering and want the code to be simple and readable. The library supports both callback style and modern async/await syntax, so you can write it however feels natural. There's also a drain hook that tells you when all work in a queue is finished, useful for triggering a "complete" action or logging. One nice detail: if you need the same queue accessible from multiple files in your project, you can pass a singleton option so they all share one queue instead of creating separate ones. The whole library is intentionally tiny, no bloat, just the core concept of sequential task execution done well.

prompts (copy fr)

prompt 1
Show me how to create a Workq queue in JavaScript that processes three file-upload jobs strictly in order.
prompt 2
Write a Workq example where a job spawns its own nested queue of subtasks that must finish before the parent continues.
prompt 3
How do I use Workq's drain hook to log a message when all queued jobs are complete?
prompt 4
Show me how to use the singleton option in Workq so multiple files in my project share the same queue.

Frequently asked questions

what is workq fr?

A lightweight JavaScript library that runs tasks one at a time in a guaranteed order, so job A always finishes before job B starts, even when jobs have their own nested sub-tasks.

What language is workq written in?

Mainly JavaScript. The stack also includes JavaScript.

Is workq actively maintained?

Dormant — no commits in 2+ years (last push 2017-11-18).

How hard is workq to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is workq for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.