Files
markitect-main/capabilities/testdrive-jsui/node_modules/@nodelib/fs.walk/README.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

6.0 KiB

@nodelib/fs.walk

A library for efficiently walking a directory recursively.

💡 Highlights

  • 💰 Returns useful information: name, path, dirent and stats (optional).
  • 🚀 On Node.js 10.10+ uses the mechanism without additional calls to determine the entry type for performance reasons. See old and modern mode.
  • ⚙️ Built-in directories/files and error filtering system.
  • 🔗 Can safely work with broken symbolic links.

Install

npm install @nodelib/fs.walk

Usage

import * as fsWalk from '@nodelib/fs.walk';

fsWalk.walk('path', (error, entries) => { /* … */ });

API

.walk(path, [optionsOrSettings], callback)

Reads the directory recursively and asynchronously. Requires a callback function.

📖 If you want to use the Promise API, use util.promisify.

fsWalk.walk('path', (error, entries) => { /* … */ });
fsWalk.walk('path', {}, (error, entries) => { /* … */ });
fsWalk.walk('path', new fsWalk.Settings(), (error, entries) => { /* … */ });

.walkStream(path, [optionsOrSettings])

Reads the directory recursively and asynchronously. Readable Stream is used as a provider.

const stream = fsWalk.walkStream('path');
const stream = fsWalk.walkStream('path', {});
const stream = fsWalk.walkStream('path', new fsWalk.Settings());

.walkSync(path, [optionsOrSettings])

Reads the directory recursively and synchronously. Returns an array of entries.

const entries = fsWalk.walkSync('path');
const entries = fsWalk.walkSync('path', {});
const entries = fsWalk.walkSync('path', new fsWalk.Settings());

path

  • Required: true
  • Type: string | Buffer | URL

A path to a file. If a URL is provided, it must use the file: protocol.

optionsOrSettings

  • Required: false
  • Type: Options | Settings
  • Default: An instance of Settings class

An Options object or an instance of Settings class.

📖 When you pass a plain object, an instance of the Settings class will be created automatically. If you plan to call the method frequently, use a pre-created instance of the Settings class.

Settings([options])

A class of full settings of the package.

const settings = new fsWalk.Settings({ followSymbolicLinks: true });

const entries = fsWalk.walkSync('path', settings);

Entry

  • name — The name of the entry (unknown.txt).
  • path — The path of the entry relative to call directory (root/unknown.txt).
  • dirent — An instance of fs.Dirent class.
  • [stats] — An instance of fs.Stats class.

Options

basePath

  • Type: string
  • Default: undefined

By default, all paths are built relative to the root path. You can use this option to set custom root path.

In the example below we read the files from the root directory, but in the results the root path will be custom.

fsWalk.walkSync('root'); // → ['root/file.txt']
fsWalk.walkSync('root', { basePath: 'custom' }); // → ['custom/file.txt']

concurrency

  • Type: number
  • Default: Infinity

The maximum number of concurrent calls to fs.readdir.

📖 The higher the number, the higher performance and the load on the File System. If you want to read in quiet mode, set the value to 4 * os.cpus().length (4 is default size of thread pool work scheduling).

deepFilter

A function that indicates whether the directory will be read deep or not.

// Skip all directories that starts with `node_modules`
const filter: DeepFilterFunction = (entry) => !entry.path.startsWith('node_modules');

entryFilter

A function that indicates whether the entry will be included to results or not.

// Exclude all `.js` files from results
const filter: EntryFilterFunction = (entry) => !entry.name.endsWith('.js');

errorFilter

A function that allows you to skip errors that occur when reading directories.

For example, you can skip ENOENT errors if required:

// Skip all ENOENT errors
const filter: ErrorFilterFunction = (error) => error.code == 'ENOENT';

stats

  • Type: boolean
  • Default: false

Adds an instance of fs.Stats class to the Entry.

📖 Always use fs.readdir with additional fs.lstat/fs.stat calls to determine the entry type.

  • Type: boolean
  • Default: false

Follow symbolic links or not. Call fs.stat on symbolic link if true.

  • Type: boolean
  • Default: true

Throw an error when symbolic link is broken if true or safely return lstat call if false.

pathSegmentSeparator

  • Type: string
  • Default: path.sep

By default, this package uses the correct path separator for your OS (\ on Windows, / on Unix-like systems). But you can set this option to any separator character(s) that you want to use instead.

fs

  • Type: FileSystemAdapter
  • Default: A default FS methods

By default, the built-in Node.js module (fs) is used to work with the file system. You can replace any method with your own.

interface FileSystemAdapter {
	lstat: typeof fs.lstat;
	stat: typeof fs.stat;
	lstatSync: typeof fs.lstatSync;
	statSync: typeof fs.statSync;
	readdir: typeof fs.readdir;
	readdirSync: typeof fs.readdirSync;
}

const settings = new fsWalk.Settings({
	fs: { lstat: fakeLstat }
});

Changelog

See the Releases section of our GitHub project for changelog for each release version.

License

This software is released under the terms of the MIT license.