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>
Features
- No dependencies
- Super lightweight & performant
- Supports nested & chained colors
- No
String.prototypemodifications - Conditional color support
- Familiar API
As of v3.0 the Chalk-style syntax (magical getter) is no longer used.
If you need or require that syntax, consider using ansi-colors, which maintains chalk parity.
Install
$ npm install --save kleur
Usage
const { red, white, blue, bold } = require('kleur');
// basic usage
red('red text');
// chained methods
blue().bold().underline('howdy partner');
// nested methods
bold(`${ white().bgRed('[ERROR]') } ${ red().italic('Something happened')}`);
Chained Methods
console.log(bold().red('this is a bold red message'));
console.log(bold().italic('this is a bold italicized message'));
console.log(bold().yellow().bgRed().italic('this is a bold yellow italicized message'));
console.log(green().bold().underline('this is a bold green underlined message'));
Nested Methods
const { yellow, red, cyan } = require('kleur');
console.log(yellow(`foo ${red().bold('red')} bar ${cyan('cyan')} baz`));
console.log(yellow('foo ' + red().bold('red') + ' bar ' + cyan('cyan') + ' baz'));
Conditional Support
Toggle color support as needed; kleur includes simple auto-detection which may not cover all cases.
const kleur = require('kleur');
// manually disable
kleur.enabled = false;
// or use another library to detect support
kleur.enabled = require('color-support').level;
console.log(kleur.red('I will only be colored red if the terminal supports colors'));
API
Any kleur method returns a String when invoked with input; otherwise chaining is expected.
It's up to the developer to pass the output to destinations like
console.log,process.stdout.write, etc.
The methods below are grouped by type for legibility purposes only. They each can be chained or nested with one another.
Colors:
black — red — green — yellow — blue — magenta — cyan — white — gray — grey
Backgrounds:
bgBlack — bgRed — bgGreen — bgYellow — bgBlue — bgMagenta — bgCyan — bgWhite
Modifiers:
reset — bold — dim — italic* — underline — inverse — hidden — strikethrough*
* Not widely supported
Benchmarks
Using Node v10.13.0
Load time
chalk :: 14.543ms
kleur :: 0.474ms
ansi-colors :: 1.923ms
Performance
# All Colors
ansi-colors x 199,381 ops/sec ±1.04% (96 runs sampled)
chalk x 12,107 ops/sec ±2.07% (87 runs sampled)
kleur x 715,334 ops/sec ±0.30% (93 runs sampled)
# Stacked colors
ansi-colors x 24,494 ops/sec ±1.03% (93 runs sampled)
chalk x 2,650 ops/sec ±2.06% (85 runs sampled)
kleur x 75,798 ops/sec ±0.19% (97 runs sampled)
# Nested colors
ansi-colors x 77,766 ops/sec ±0.32% (94 runs sampled)
chalk x 5,596 ops/sec ±1.85% (86 runs sampled)
kleur x 137,660 ops/sec ±0.31% (93 runs sampled)
Credits
This project originally forked Brian Woodward's awesome ansi-colors library.
Beginning with kleur@3.0, the Chalk-style syntax (magical getter) has been replaced with function calls per key:
// Old:
c.red.bold.underline('old');
// New:
c.red().bold().underline('new');
As I work more with Rust, the newer syntax feels so much better & more natural!
If you prefer the old syntax, you may migrate to ansi-colors. Versions below kleur@3.0 have been deprecated.
License
MIT © Luke Edwards
