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>
102 lines
2.7 KiB
Markdown
102 lines
2.7 KiB
Markdown
# p-limit
|
|
|
|
> Run multiple promise-returning & async functions with limited concurrency
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install p-limit
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const pLimit = require('p-limit');
|
|
|
|
const limit = pLimit(1);
|
|
|
|
const input = [
|
|
limit(() => fetchSomething('foo')),
|
|
limit(() => fetchSomething('bar')),
|
|
limit(() => doSomething())
|
|
];
|
|
|
|
(async () => {
|
|
// Only one promise is run at once
|
|
const result = await Promise.all(input);
|
|
console.log(result);
|
|
})();
|
|
```
|
|
|
|
## API
|
|
|
|
### pLimit(concurrency)
|
|
|
|
Returns a `limit` function.
|
|
|
|
#### concurrency
|
|
|
|
Type: `number`\
|
|
Minimum: `1`\
|
|
Default: `Infinity`
|
|
|
|
Concurrency limit.
|
|
|
|
### limit(fn, ...args)
|
|
|
|
Returns the promise returned by calling `fn(...args)`.
|
|
|
|
#### fn
|
|
|
|
Type: `Function`
|
|
|
|
Promise-returning/async function.
|
|
|
|
#### args
|
|
|
|
Any arguments to pass through to `fn`.
|
|
|
|
Support for passing arguments on to the `fn` is provided in order to be able to avoid creating unnecessary closures. You probably don't need this optimization unless you're pushing a *lot* of functions.
|
|
|
|
### limit.activeCount
|
|
|
|
The number of promises that are currently running.
|
|
|
|
### limit.pendingCount
|
|
|
|
The number of promises that are waiting to run (i.e. their internal `fn` was not called yet).
|
|
|
|
### limit.clearQueue()
|
|
|
|
Discard pending promises that are waiting to run.
|
|
|
|
This might be useful if you want to teardown the queue at the end of your program's lifecycle or discard any function calls referencing an intermediary state of your app.
|
|
|
|
Note: This does not cancel promises that are already running.
|
|
|
|
## FAQ
|
|
|
|
### How is this different from the [`p-queue`](https://github.com/sindresorhus/p-queue) package?
|
|
|
|
This package is only about limiting the number of concurrent executions, while `p-queue` is a fully featured queue implementation with lots of different options, introspection, and ability to pause the queue.
|
|
|
|
## Related
|
|
|
|
- [p-queue](https://github.com/sindresorhus/p-queue) - Promise queue with concurrency control
|
|
- [p-throttle](https://github.com/sindresorhus/p-throttle) - Throttle promise-returning & async functions
|
|
- [p-debounce](https://github.com/sindresorhus/p-debounce) - Debounce promise-returning & async functions
|
|
- [p-all](https://github.com/sindresorhus/p-all) - Run promise-returning & async functions concurrently with optional limited concurrency
|
|
- [More…](https://github.com/sindresorhus/promise-fun)
|
|
|
|
---
|
|
|
|
<div align="center">
|
|
<b>
|
|
<a href="https://tidelift.com/subscription/pkg/npm-p-limit?utm_source=npm-p-limit&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>
|