wtf is workq?

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.