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>
The UNIX command rm -rf for node.
Install with npm install rimraf, or just drop rimraf.js somewhere.
API
rimraf(f, [opts], callback)
The first parameter will be interpreted as a globbing pattern for files. If you
want to disable globbing you can do so with opts.disableGlob (defaults to
false). This might be handy, for instance, if you have filenames that contain
globbing wildcard characters.
The callback will be called with an error if there is one. Certain errors are handled for you:
- Windows:
EBUSYandENOTEMPTY- rimraf will back off a maximum ofopts.maxBusyTriestimes before giving up, adding 100ms of wait between each attempt. The defaultmaxBusyTriesis 3. ENOENT- If the file doesn't exist, rimraf will return successfully, since your desired outcome is already the case.EMFILE- Sincereaddirrequires opening a file descriptor, it's possible to hitEMFILEif too many file descriptors are in use. In the sync case, there's nothing to be done for this. But in the async case, rimraf will gradually back off with timeouts up toopts.emfileWaitms, which defaults to 1000.
options
-
unlink, chmod, stat, lstat, rmdir, readdir, unlinkSync, chmodSync, statSync, lstatSync, rmdirSync, readdirSync
In order to use a custom file system library, you can override specific fs functions on the options object.
If any of these functions are present on the options object, then the supplied function will be used instead of the default fs method.
Sync methods are only relevant for
rimraf.sync(), of course.For example:
var myCustomFS = require('some-custom-fs') rimraf('some-thing', myCustomFS, callback) -
maxBusyTries
If an
EBUSY,ENOTEMPTY, orEPERMerror code is encountered on Windows systems, then rimraf will retry with a linear backoff wait of 100ms longer on each try. The default maxBusyTries is 3.Only relevant for async usage.
-
emfileWait
If an
EMFILEerror is encountered, then rimraf will retry repeatedly with a linear backoff of 1ms longer on each try, until the timeout counter hits this max. The default limit is 1000.If you repeatedly encounter
EMFILEerrors, then consider using graceful-fs in your program.Only relevant for async usage.
-
glob
Set to
falseto disable glob pattern matching.Set to an object to pass options to the glob module. The default glob options are
{ nosort: true, silent: true }.Glob version 6 is used in this module.
Relevant for both sync and async usage.
-
disableGlob
Set to any non-falsey value to disable globbing entirely. (Equivalent to setting
glob: false.)
rimraf.sync
It can remove stuff synchronously, too. But that's not so good. Use the async API. It's better.
CLI
If installed with npm install rimraf -g it can be used as a global
command rimraf <path> [<path> ...] which is useful for cross platform support.
mkdirp
If you need to create a directory recursively, check out mkdirp.