nyc 18.x

Use nyc 18.x for its CommonJS API, coverage-file lifecycle, directory resolution, and CLI/runner boundaries. Covers the Node runtime change from nyc 17.x and avoids standalone examples that depend on runner or subprocess internals.

For

nyc@18.0.0

Verified

2026-09-08, 3 examples executed

Package

@modootoday/pmcp-nyc@18.0.0

What it covers

• Runtime and package shape
• Instrumentation
• Coverage files
• Temporary directories, reset, and reports
• CLI and runner boundary
• Configuration loading
• What this skill does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

const assert = require('node:assert/strict')
const NYC = require('nyc')
const path = require('node:path')

const nyc = new NYC({
  cwd: '/workspace/project',
  tempDirectory: '.coverage-data',
  reportDir: 'artifacts/coverage',
  reporter: ['text', 'lcov']
})

assert.equal(nyc.cwd, '/workspace/project')
assert.deepEqual(nyc.reporter, ['text', 'lcov'])
assert.equal(nyc.tempDirectory(), path.resolve('/workspace/project', '.coverage-data'))
assert.equal(nyc.reportDirectory(), path.resolve('/workspace/project', 'artifacts/coverage'))

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-nyc

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.