Files
markitect-main/capabilities/testdrive-jsui/node_modules/rimraf/CHANGELOG.md
tegwick 17c62aadaa feat: complete testdrive-jsui capability extraction with full JavaScript test integration
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>
2025-11-09 22:29:30 +01:00

1.5 KiB

v3.0

  • Add --preserve-root option to executable (default true)
  • Drop support for Node.js below version 6

v2.7

  • Make glob an optional dependency

2.6

  • Retry on EBUSY on non-windows platforms as well
  • Make rimraf.sync 10000% more reliable on Windows

2.5

  • Handle Windows EPERM when lstat-ing read-only dirs
  • Add glob option to pass options to glob

2.4

  • Add EPERM to delay/retry loop
  • Add disableGlob option

2.3

  • Make maxBusyTries and emfileWait configurable
  • Handle weird SunOS unlink-dir issue
  • Glob the CLI arg for better Windows support

2.2

  • Handle ENOENT properly on Windows
  • Allow overriding fs methods
  • Treat EPERM as indicative of non-empty dir
  • Remove optional graceful-fs dep
  • Consistently return null error instead of undefined on success
  • win32: Treat ENOTEMPTY the same as EBUSY
  • Add rimraf binary

2.1

  • Fix SunOS error code for a non-empty directory
  • Try rmdir before readdir
  • Treat EISDIR like EPERM
  • Remove chmod
  • Remove lstat polyfill, node 0.7 is not supported

2.0

  • Fix myGid call to check process.getgid
  • Simplify the EBUSY backoff logic.
  • Use fs.lstat in node >= 0.7.9
  • Remove gently option
  • remove fiber implementation
  • Delete files that are marked read-only

1.0

  • Allow ENOENT in sync method
  • Throw when no callback is provided
  • Make opts.gently an absolute path
  • use 'stat' if 'lstat' is not available
  • Consistent error naming, and rethrow non-ENOENT stat errors
  • add fiber implementation