npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pokujs/multi-suite

v1.0.2

Published

A Poku plugin to run multiple independent test suites as a single, unified execution.

Downloads

1,129

Readme

@pokujs/multi-suite

Enjoying Poku? Give him a star to show your support 🌟


📚 Documentation


🧬 @pokujs/multi-suite is a Poku plugin to run multiple independent test suites (each with its own configuration) as a single, unified execution.

[!TIP]

  • Run multiple suites as one: independent concurrency, reporters, plugins, and quiet mode per suite, with isolated executions and a single consolidated report at the end.
  • Combine with @pokujs/coverage to merge the suites automatically on teardown.

Quickstart

Install

# Node.js
npm i -D @pokujs/multi-suite
# Bun
bun add -d @pokujs/multi-suite
# Deno (optional)
deno add npm:@pokujs/multi-suite

Enable the Plugin

// poku.config.js
import { multiSuite } from '@pokujs/multi-suite';
import { defineConfig } from 'poku';

export default defineConfig({
  plugins: [
    multiSuite([
      { include: 'test/unit', concurrency: 8 },
      { include: 'test/integration', sequential: true },
    ]),
  ],
});

Suite Options

Each suite accepts all poku config file options, applied independently.


Examples

Different concurrency per suite

multiSuite([
  { include: 'test/unit', concurrency: 16 },
  { include: 'test/e2e', sequential: true },
]);

Load env files per suite

multiSuite([
  { include: 'test/unit', envFile: '.env.test' },
  { include: 'test/integration', envFile: '.env.integration' },
]);

Scoped plugins per suite

multiSuite([
  { include: 'test/unit' },
  { include: 'test/integration', plugins: [myPlugin()] },
]);

Different reporter per suite

multiSuite([
  { include: 'test/unit', reporter: 'dot' },
  { include: 'test/integration', reporter: 'compact' },
]);

Kill ports before a suite

multiSuite([
  { include: 'test/unit' },
  {
    include: 'test/integration',
    kill: { port: [3000, 5432] },
  },
]);

How It Works

  • Suites run sequentially, one after the other
  • Each suite is a fully independent poku execution with its own configuration
  • Live file results are shown as they happen, using each suite's configured reporter
  • A single consolidated failure report and summary badge are shown at the end
  • Ctrl+C stops everything immediately

License

MIT © wellwelwel