vibe-queue

library1.1.3jsnpmunverified

Vibe Queue is a CLI task manager and execution engine with a real-time dashboard, designed for modern developer workflows. Version 1.1.3 is the current stable release. It features live process monitoring, on-the-fly TypeScript compilation via esbuild-wasm, automatic network discovery, and self-signed HTTPS certificate generation. Configuration is done via .vibe-queue/ directory files (queue.yaml, tasks.jsonc) and environment variables. Releases follow semantic versioning.

devops

npm install vibe-queue

package ↗

INSTALL

IMPORT

SIG · VIBE-QUEUE

vibe-queue

devopsjavascriptv1.1.3

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

vibeq

✓ npx vibeq

✗ not applicable as a CLI tool; global install via npm install -g vibe-queue

Global CLI command; no programmatic import

start

✓ npm start

✗ node server.js (if you try to run internal modules directly)

npm start runs the full system (Server + Runner); internal modules are not exported

lint

✓ npm run lint

✗ tsc --noEmit (deprecated, use npm run lint)

Linting uses TypeScript type checks; npm run lint is the official command

Installs vibe-queue globally, launches the CLI and dashboard on localhost:3000.

npm install -g vibe-queue vibeq # Dashboard available at http://localhost:3000

Debug

Known issues

gotchaDashboard runs on port 3000 by default; ensure port is free or set VIBE_QUEUE_PORT env variable

fix

Set VIBE_QUEUE_PORT environment variable to a different port

affects: >=1.0.0

gotchaHTTPS is disabled by default; enable with VIBE_QUEUE_HTTPS=true, but requires self-signed certificate generation which may cause browser warnings

fix

Set VIBE_QUEUE_HTTPS=true and accept self-signed certificate in browser

affects: >=1.0.0

gotchaConfiguration files (queue.yaml, tasks.jsonc) must be placed in .vibe-queue/ directory; missing directory causes errors

fix

Create a .vibe-queue/ directory in your project root and add required files

affects: >=1.0.0

breakingesbuild-wasm dependency may not work in all Node.js environments (e.g., some CI runners with restricted WASM support)

fix

Ensure Node.js version supports WASM (>=12.x recommended) and environment allows WASM execution

affects: >=1.0.0

gotchaGlobal install may require sudo on Unix systems; failing to use -g flag results in command not found

fix

Install globally with npm install -g vibe-queue, or use npx vibe-queue

affects: >=1.0.0

Errors

Common errors & fixes

command not found: vibeq

vibe-queue not installed globally or not in PATH

fix

Run npm install -g vibe-queue or use npx vibeq

Error: listen EADDRINUSE :::3000

Port 3000 already in use

fix

Set VIBE_QUEUE_PORT environment variable to an available port

Error: Cannot find module 'esbuild-wasm'

esbuild-wasm dependency missing due to incomplete install

fix

Run npm install in the project directory where vibe-queue is installed

Upgrade

Version history

1.1.3latest on npm

Audit

Dependencies

esbuild-wasmrequiredOn-the-fly TypeScript compilation

Agent activity

5 hits · last 30 days

node

Amazon

Resources

packagevibe-queue ↗