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>
94 lines
2.6 KiB
Markdown
94 lines
2.6 KiB
Markdown
# @tootallnate/once
|
|
|
|
### Creates a Promise that waits for a single event
|
|
|
|
## Installation
|
|
|
|
Install with `npm`:
|
|
|
|
```bash
|
|
$ npm install @tootallnate/once
|
|
```
|
|
|
|
## API
|
|
|
|
### once(emitter: EventEmitter, name: string, opts?: OnceOptions): Promise<[...Args]>
|
|
|
|
Creates a Promise that waits for event `name` to occur on `emitter`, and resolves
|
|
the promise with an array of the values provided to the event handler. If an
|
|
`error` event occurs before the event specified by `name`, then the Promise is
|
|
rejected with the error argument.
|
|
|
|
```typescript
|
|
import once from '@tootallnate/once';
|
|
import { EventEmitter } from 'events';
|
|
|
|
const emitter = new EventEmitter();
|
|
|
|
setTimeout(() => {
|
|
emitter.emit('foo', 'bar');
|
|
}, 100);
|
|
|
|
const [result] = await once(emitter, 'foo');
|
|
console.log({ result });
|
|
// { result: 'bar' }
|
|
```
|
|
|
|
#### Promise Strong Typing
|
|
|
|
The main feature that this module provides over other "once" implementations is that
|
|
the Promise that is returned is _**strongly typed**_ based on the type of `emitter`
|
|
and the `name` of the event. Some examples are shown below.
|
|
|
|
_The process "exit" event contains a single number for exit code:_
|
|
|
|
```typescript
|
|
const [code] = await once(process, 'exit');
|
|
// ^ number
|
|
```
|
|
_A child process "exit" event contains either an exit code or a signal:_
|
|
|
|
```typescript
|
|
const child = spawn('echo', []);
|
|
const [code, signal] = await once(child, 'exit');
|
|
// ^ number | null
|
|
// ^ string | null
|
|
```
|
|
|
|
_A forked child process "message" event is type `any`, so you can cast the Promise directly:_
|
|
|
|
```typescript
|
|
const child = fork('file.js');
|
|
|
|
// With `await`
|
|
const [message, _]: [WorkerPayload, unknown] = await once(child, 'message');
|
|
|
|
// With Promise
|
|
const messagePromise: Promise<[WorkerPayload, unknown]> = once(child, 'message');
|
|
|
|
// Better yet would be to leave it as `any`, and validate the payload
|
|
// at runtime with i.e. `ajv` + `json-schema-to-typescript`
|
|
```
|
|
|
|
_If the TypeScript definition does not contain an overload for the specified event name, then the Promise will have type `unknown[]` and your code will need to narrow the result manually:_
|
|
|
|
```typescript
|
|
interface CustomEmitter extends EventEmitter {
|
|
on(name: 'foo', listener: (a: string, b: number) => void): this;
|
|
}
|
|
|
|
const emitter: CustomEmitter = new EventEmitter();
|
|
|
|
// "foo" event is a defined overload, so it's properly typed
|
|
const fooPromise = once(emitter, 'foo');
|
|
// ^ Promise<[a: string, b: number]>
|
|
|
|
// "bar" event in not a defined overload, so it gets `unknown[]`
|
|
const barPromise = once(emitter, 'bar');
|
|
// ^ Promise<unknown[]>
|
|
```
|
|
|
|
### OnceOptions
|
|
|
|
- `signal` - `AbortSignal` instance to unbind event handlers before the Promise has been fulfilled.
|