Quick
A quick Bijection component for Bijection.
git clone https://github.com/bijectionhq/quick.git
cd quick
git checkout 45e3a3cd357335444c4357e5e506343268f4755eBijection repository access is required. Request access.
Description
A quick Bijection component for Bijection.
Explore the package README for API concepts, configuration, and examples. Check the Bijection source for adaptation-specific setup.
Review the source and its dependencies before adopting this package. Source availability does not establish npm publication or runtime qualification.
Getting started
- Get the source at the revision above and read its package documentation.
- Check the required Bijection SDK version, dependencies, and external service credentials.
- Follow the package setup instructions and the guide to using components.
- Exercise the component in your deployment according to your project’s verification rules.
Open source
Maintained source: bijectionhq/quick. Based on danthegoodman1/quick-convex. License: Apache-2.0. Consult the repository for license terms, notices, and contributor attribution.
From the upstream publisher
A quick convex component for Convex.
Upstream package FAQ
What's the difference between FIFO and vesting modes in quick-convex?
FIFO mode enforces strict ordering per queueId where delayed items block subsequent items in the same queue. Vesting mode prioritizes throughput, allowing ready items to run immediately even if earlier items are delayed or retrying. Use FIFO for strict ordering requirements and vesting for maximum throughput.
How does quick-convex compare to Convex Workpools?
quick-convex offers multiple ordering modes including strict FIFO per domain, while Workpools are lighter weight and officially maintained. quick-convex handles scale-up patterns better and retries onComplete failures, but has more overhead per job at low volumes. Both are production-ready solutions.
Can I use different retry policies for different jobs?
Yes, quick-convex supports retry configuration at multiple levels. Set defaults when creating the Quick instance, then override per job with retry: false, retry: true, or retry: { maxAttempts, initialBackoffMs, base } for custom behavior.
How do I handle job completion and cleanup with quick-convex?
Use the onComplete callback which runs as a mutation after both successful and failed jobs. quick-convex persists completion state and retries the onComplete handler up to 2 times on failures, ensuring reliable cleanup and post-processing logic.
Use with agents and CLI
Give your coding agent the component’s source identity and setup guidance.
Help me integrate Quick with Bijection.
Read: https://bijection.com/components/quick/SKILL.md
Check SDK compatibility and dependency availability.
Follow this project's execution and verification rules.Upstream README.md
View repository ↗Documentation from danthegoodman1/quick-convex at its recorded upstream revision. APIs and setup may differ in the Bijection adaptation.
Loading package documentation…