codeql-action/node_modules/npm-run-path
dependabot[bot] 19f00dc212
Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576)
* Bump @ava/typescript from 3.0.1 to 4.0.0

Bumps [@ava/typescript](https://github.com/avajs/typescript) from 3.0.1 to 4.0.0.
- [Release notes](https://github.com/avajs/typescript/releases)
- [Commits](https://github.com/avajs/typescript/compare/v3.0.1...v4.0.0)

---
updated-dependencies:
- dependency-name: "@ava/typescript"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update checked-in dependencies

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions@github.com>
2023-03-13 14:10:40 -07:00
..
node_modules/path-key Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576) 2023-03-13 14:10:40 -07:00
index.d.ts Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576) 2023-03-13 14:10:40 -07:00
index.js Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576) 2023-03-13 14:10:40 -07:00
license Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576) 2023-03-13 14:10:40 -07:00
package.json Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576) 2023-03-13 14:10:40 -07:00
readme.md Bump @ava/typescript from 3.0.1 to 4.0.0 (#1576) 2023-03-13 14:10:40 -07:00

readme.md

npm-run-path

Get your PATH prepended with locally installed binaries

In npm run scripts you can execute locally installed binaries by name. This enables the same outside npm.

Install

npm install npm-run-path

Usage

import childProcess from 'node:child_process';
import {npmRunPath, npmRunPathEnv} from 'npm-run-path';

console.log(process.env.PATH);
//=> '/usr/local/bin'

console.log(npmRunPath());
//=> '/Users/sindresorhus/dev/foo/node_modules/.bin:/Users/sindresorhus/dev/node_modules/.bin:/Users/sindresorhus/node_modules/.bin:/Users/node_modules/.bin:/node_modules/.bin:/usr/local/bin'

// `foo` is a locally installed binary
childProcess.execFileSync('foo', {
	env: npmRunPathEnv()
});

API

npmRunPath(options?)

Returns the augmented PATH string.

options

Type: object

cwd

Type: string | URL
Default: process.cwd()

The working directory.

path

Type: string
Default: PATH

The PATH to be appended.

Set it to an empty string to exclude the default PATH.

execPath

Type: string
Default: process.execPath

The path to the current Node.js executable. Its directory is pushed to the front of PATH.

This can be either an absolute path or a path relative to the cwd option.

npmRunPathEnv(options?)

Returns the augmented process.env object.

options

Type: object

cwd

Type: string | URL
Default: process.cwd()

The working directory.

env

Type: object

Accepts an object of environment variables, like process.env, and modifies the PATH using the correct PATH key. Use this if you're modifying the PATH for use in the child_process options.

execPath

Type: string
Default: process.execPath

The path to the Node.js executable to use in child processes if that is different from the current one. Its directory is pushed to the front of PATH.

This can be either an absolute path or a path relative to the cwd option.


Get professional support for this package with a Tidelift subscription
Tidelift helps make open source sustainable for maintainers while giving companies
assurances about security, maintenance, and licensing for their dependencies.