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/monocart

v1.1.0

Published

☔️ A Poku plugin for V8 code coverage.

Readme

@pokujs/monocart

Enjoying Poku? Give him a star to show your support


📚 Documentation


☔️ @pokujs/monocart is a Poku plugin for native V8 code coverage using monocart-coverage-reports.

[!TIP]

@pokujs/monocart supports JSONC config files (mcr.config.json, mcr.config.jsonc) out of the box, allowing comments in your configuration. You can also use JS, CJS, MJS, and TS config files, or set options directly in the plugin.


Quickstart

Install

npm i -D @pokujs/monocart

Usage

// poku.config.js
import { coverage } from '@pokujs/monocart';
import { defineConfig } from 'poku';

export default defineConfig({
  plugins: [coverage()],
});

Run poku and a coverage report will be generated after your test results.

[!IMPORTANT]

This plugin relies on Node.js' built-in NODE_V8_COVERAGE environment variable to collect coverage data. Bun and Deno do not support this mechanism, so coverage data will not be collected when running tests with these runtimes.


Options

The plugin accepts all monocart-coverage-reports options plus two plugin-specific options:

coverage({
  // Plugin options
  requireFlag: true, // default: false — require `--coverage` CLI flag to activate
  config: 'mcr.config.js', // default: auto-discover — custom MCR config file path, or `false` to skip

  // All monocart-coverage-reports options are supported, for example:
  reports: ['v8', 'console-details'],
  outputDir: './coverage-reports',
  entryFilter: { '**/node_modules/**': false, '**/src/**': true },
  sourceFilter: { '**/src/**': true },
  lcov: true,
  watermarks: [50, 80],
  all: './src',
  // ...
});

Examples

Console coverage details

coverage({
  reports: ['console-details'],
  filter: { '**/node_modules/**': false, '**/src/**': true },
});

Generate V8 HTML and LCOV reports

coverage({
  reports: ['v8', 'lcovonly'],
  filter: { '**/node_modules/**': false, '**/src/**': true },
});

Multiple reporters

coverage({
  reports: [
    'v8',
    'console-details',
    'codecov',
    ['lcovonly', { file: 'lcov.info' }],
  ],
  filter: { '**/node_modules/**': false, '**/src/**': true },
});

Include untested files

coverage({
  reports: ['console-details'],
  filter: { '**/node_modules/**': false, '**/src/**': true },
  all: './src',
});

Enforce coverage thresholds

Use the onEnd hook from monocart-coverage-reports:

coverage({
  reports: ['console-details'],
  filter: { '**/node_modules/**': false, '**/src/**': true },
  onEnd: (results) => {
    const { summary } = results;
    if (summary.lines.pct < 80) {
      console.error(`Lines coverage ${summary.lines.pct}% is below 80%`);
      process.exitCode = 1;
    }
  },
});

Require --coverage flag

By default, coverage runs whenever the plugin is active. Use requireFlag to only collect coverage when --coverage is passed to the CLI, keeping watch mode, debugging, and filtered runs fast:

coverage({
  reports: ['console-details'],
  filter: { '**/node_modules/**': false, '**/src/**': true },
  requireFlag: true,
});
# No coverage (plugin is a no-op)
poku test/

# With coverage
poku --coverage test/

Using a config file

Use any monocart-coverage-reports config file (mcr.config.js, mcr.config.cjs, mcr.config.mjs, mcr.config.json, mcr.config.jsonc, mcr.config.ts):

// mcr.config.js
export default {
  reports: ['v8', 'console-details', 'codecov'],
  filter: { '**/node_modules/**': false, '**/src/**': true },
};

JSONC config files support comments:

// mcr.config.jsonc
{
  // V8 and console reports
  "reports": ["v8", "console-details"],
  "filter": {
    "**/node_modules/**": false,
    "**/src/**": true,
  },
}
// poku.config.js
coverage({
  config: 'mcr.config.jsonc', // or false to disable config file discovery
});

When no config is specified, the plugin automatically searches for mcr.config.json, and mcr.config.jsonc in the working directory, and monocart-coverage-reports searches for mcr.config.js, mcr.config.cjs, mcr.config.mjs, and mcr.config.ts.

You can also specify the config path via CLI:

poku --coverageConfig=mcr.config.jsonc test/

[!NOTE]

Priority order:

  • For config file discovery: --coverageConfig (CLI) > config (plugin option) > auto-discovery
  • For coverage options: plugin options > config file options

How It Works

  • setup creates a temp directory and sets NODE_V8_COVERAGE — every test process spawned by Poku automatically writes V8 coverage data
  • teardown uses monocart-coverage-reports to read coverage data from the temp directory, generate reports, then cleans up
  • No modification to test commands or runner configuration needed

License

MIT © wellwelwel and contributors.