AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomspoku
Poku is a lightweight, zero-dependency test runner for Node.js, Bun, and Deno that emphasizes cross-platform compatibility and ease of use. It provides core testing utilities (assertions, test organization, process control) with a focus on performance and minimal setup overhead.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | wellwelwel/poku |
| Owner | wellwelwel |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 1.2k |
| Forks | 27 |
| Open issues | 2 |
| Latest release | v4.5.0 (2026-06-18) |
| Last updated | 2026-06-18 |
| Source | https://github.com/wellwelwel/poku |
What poku is
TypeScript-based test runner supporting ESM, CommonJS, and TypeScript with per-file test isolation, built-in process/port management, and optional Docker integration. Achieves performance gains (~5.3x faster than Jest) through selective test execution and lightweight dependency footprint (~145x smaller than Jest).
Get the poku source
Clone the repository and explore it locally.
git clone https://github.com/wellwelwel/poku.gitcd poku# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Explicit async/await handling required per documentation FAQ; implicit Promise handling differs from Jest/Vitest.
- Per-file test isolation is enforced; shared test state patterns common in Jest require restructuring.
- Plugin architecture available but maturity of third-party plugins unknown; Docker and coverage are official plugins requiring separate opt-in.
- Configuration via file (poku.config.ts/.js) or CLI; integration with existing build/config tooling (ESLint, TypeScript, etc.) unclear.
- Watch mode available but selective re-run logic and performance under large test suites requires validation.
When to avoid it — and what to weigh
- Heavy reliance on snapshot testing — Poku's assertion API mirrors Node.js built-ins; snapshot management is not mentioned. Projects requiring sophisticated snapshot workflows may need plugins or custom solutions.
- Requires integrated code coverage UI or reports — Coverage is available via optional plugin but integration depth and reporting format options are not detailed. Complex coverage analysis workflows may require supplementary tools.
- Team dependent on IDE/editor test runners — No evidence of IDE plugin ecosystem (VS Code, WebStorm, etc.). Teams relying on IDE-native test execution and debugging may face friction.
- Established Jest/Vitest test suites — Migration from Jest (v3→v4 breaking changes noted) or Vitest requires refactoring test structure and assertion syntax. Cost-benefit only clear for greenfield projects.
License & commercial use
MIT License (OSI-approved). Permissive, allows commercial use, modification, and distribution with attribution. No restrictions on proprietary derivative works.
MIT License explicitly permits commercial use, closed-source modifications, and sublicensing. However, validate any bundled third-party dependencies (none documented as zero-dependency) and review SECURITY.md for vulnerability disclosure before production deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
Project maintains SECURITY.md policy (specifics not provided in data). Zero-dependency design reduces supply-chain attack surface. Process/port management and Docker integration introduce OS-level interaction surface; validate container image sources and process isolation when used in untrusted environments. Consider security implications of running arbitrary test processes during CI.
Alternatives to consider
Vitest
Faster, lighter-weight than Jest with ESM-first design; stronger IDE plugin ecosystem. Trade-off: ~4.5x slower than Poku, ~124x heavier, but mature plugin ecosystem and snapshot support.
Jest
Industry-standard, mature, large ecosystem; excels at snapshot testing and IDE integration. Trade-off: ~5.3x slower than Poku, ~145x heavier, Node.js-only (no Bun/Deno).
uvu
Lightweight, fast, cross-platform Node.js/Deno runtime support. Trade-off: ~2.8x heavier than Poku, no built-in process/Docker helpers, smaller community.
Build on poku with DEV.co software developers
Poku cuts test setup and execution overhead for multi-runtime JavaScript projects. Ideal for CI cost reduction and cross-platform library development. Review SECURITY.md and migration path before production adoption.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
poku FAQ
Does Poku work with existing Jest/Vitest tests?
Can Poku run in CI without installing Node.js separately?
Is there a watch mode for rapid development iteration?
What is the plugin ecosystem maturity?
Senior engineers for your next build
The gap between a working poku demo and a supportable open-source testing system is where DEV.co works. We offer custom software development and web development services for exactly that stretch.
Lightweight Testing Across Runtimes
Poku cuts test setup and execution overhead for multi-runtime JavaScript projects. Ideal for CI cost reduction and cross-platform library development. Review SECURITY.md and migration path before production adoption.