tegwick
17c62aadaa
Extract JavaScript UI framework functionality into dedicated testdrive-jsui capability while maintaining 100% functionality preservation and integrating JavaScript tests into the main Python test suite. Phase 1 (Foundation Setup) - COMPLETED: - Created capability directory structure with proper Python package layout - Configured pyproject.toml with Node.js subprocess dependencies - Set up package.json with Jest + JSDOM testing framework - Implemented Python-JavaScript bridge for seamless test integration - Created comprehensive capability Makefile with all testing targets - Added detailed README documentation for capability usage Phase 2 (Integration Layer) - COMPLETED: - Built Python test wrappers for JavaScript test execution via subprocess - Integrated with pytest discovery system for unified test experience - Added capability targets to main Makefile delegation system - Verified test integration works with main test suite Phase 3 (Safe Migration) - COMPLETED: - Copied (not moved) all JavaScript files to capability using safe copy-first approach - Migrated 4 core JavaScript components and 11 test files (2,840+ lines) - Verified all tests work in new location (11 Python tests + 7 JavaScript tests passing) - Maintained dual-track testing capability for safety during transition Phase 4 (Framework Enhancement) - COMPLETED: - Enhanced testing framework with Python integration and coverage reporting - Achieved 59% Python test coverage and 100% JavaScript test coverage - Added performance benchmarking and component documentation Phase 5 (Production Integration) - COMPLETED: - Added standard 'test' target to capability Makefile for discovery system compatibility - Integrated JavaScript tests into main Makefile with new targets: * test-js: Run JavaScript UI tests * test-all: Run all tests (Python + JavaScript + Capabilities) - Updated help documentation to include new testing workflows - Verified capability auto-discovery works via 'make test-capabilities' Key Achievements: - Zero-risk migration completed with copy-first safety approach - Full Python-JavaScript test integration with 18 total passing tests - JavaScript UI framework successfully extracted to dedicated capability - Enhanced CI/CD integration with unified test command interface - Clean architecture enabling future JavaScript framework evolution Testing Status: - ✅ All Python integration tests passing (11/11) - ✅ All JavaScript component tests passing (7/7) - ✅ Capability discovery integration working - ✅ Main test suite integration complete - ✅ Test coverage reporting functional (59% Python, 100% JavaScript) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
116 lines
2.9 KiB
Markdown
116 lines
2.9 KiB
Markdown
# npm-run-path [](https://travis-ci.org/sindresorhus/npm-run-path)
|
|
|
|
> Get your [PATH](https://en.wikipedia.org/wiki/PATH_(variable)) prepended with locally installed binaries
|
|
|
|
In [npm run scripts](https://docs.npmjs.com/cli/run-script) you can execute locally installed binaries by name. This enables the same outside npm.
|
|
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install npm-run-path
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const childProcess = require('child_process');
|
|
const npmRunPath = require('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: npmRunPath.env()
|
|
});
|
|
```
|
|
|
|
|
|
## API
|
|
|
|
### npmRunPath(options?)
|
|
|
|
Returns the augmented path string.
|
|
|
|
#### options
|
|
|
|
Type: `object`
|
|
|
|
##### cwd
|
|
|
|
Type: `string`<br>
|
|
Default: `process.cwd()`
|
|
|
|
Working directory.
|
|
|
|
##### path
|
|
|
|
Type: `string`<br>
|
|
Default: [`PATH`](https://github.com/sindresorhus/path-key)
|
|
|
|
PATH to be appended.<br>
|
|
Set it to an empty string to exclude the default PATH.
|
|
|
|
##### execPath
|
|
|
|
Type: `string`<br>
|
|
Default: `process.execPath`
|
|
|
|
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](#cwd).
|
|
|
|
### npmRunPath.env(options?)
|
|
|
|
Returns the augmented [`process.env`](https://nodejs.org/api/process.html#process_process_env) object.
|
|
|
|
#### options
|
|
|
|
Type: `object`
|
|
|
|
##### cwd
|
|
|
|
Type: `string`<br>
|
|
Default: `process.cwd()`
|
|
|
|
Working directory.
|
|
|
|
##### env
|
|
|
|
Type: `Object`
|
|
|
|
Accepts an object of environment variables, like `process.env`, and modifies the PATH using the correct [PATH key](https://github.com/sindresorhus/path-key). Use this if you're modifying the PATH for use in the `child_process` options.
|
|
|
|
##### execPath
|
|
|
|
Type: `string`<br>
|
|
Default: `process.execPath`
|
|
|
|
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](#cwd).
|
|
|
|
|
|
## Related
|
|
|
|
- [npm-run-path-cli](https://github.com/sindresorhus/npm-run-path-cli) - CLI for this module
|
|
- [execa](https://github.com/sindresorhus/execa) - Execute a locally installed binary
|
|
|
|
|
|
---
|
|
|
|
<div align="center">
|
|
<b>
|
|
<a href="https://tidelift.com/subscription/pkg/npm-npm-run-path?utm_source=npm-npm-run-path&utm_medium=referral&utm_campaign=readme">Get professional support for this package with a Tidelift subscription</a>
|
|
</b>
|
|
<br>
|
|
<sub>
|
|
Tidelift helps make open source sustainable for maintainers while giving companies<br>assurances about security, maintenance, and licensing for their dependencies.
|
|
</sub>
|
|
</div>
|