npm-run-path 6.x

Use npm-run-path ^6.0.0 to construct npm-style PATH values or environment objects for Node child processes.

For: npm-run-path@6.0.0
Verified: 2026-09-08, 3 examples executed
Package: @modootoday/pmcp-npm-run-path@6.0.0

What it covers

API
`npmRunPath(options?): string`
`npmRunPathEnv(options?): ProcessEnv`
Examples
Construct a PATH and an environment
Pass the generated environment to a child process
Use the options supported by the current type surface
Common mistakes
Not covered

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.

import assert from 'node:assert/strict';
import {npmRunPath, npmRunPathEnv} from 'npm-run-path';

const path = npmRunPath({
  path: '/usr/bin',
  preferLocal: false,
  addExecPath: false,
});

assert.equal(path, '/usr/bin');

const env = npmRunPathEnv({
  env: {
    PATH: '/usr/bin',
    CUSTOM_VALUE: 'kept',
  },
  preferLocal: false,
  addExecPath: false,
});

assert.equal(env.PATH, '/usr/bin');
assert.equal(env.CUSTOM_VALUE, 'kept');

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-npm-run-path

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