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>
127 lines
3.0 KiB
Markdown
127 lines
3.0 KiB
Markdown
# @nodelib/fs.stat
|
|
|
|
> Get the status of a file with some features.
|
|
|
|
## :bulb: Highlights
|
|
|
|
Wrapper around standard method `fs.lstat` and `fs.stat` with some features.
|
|
|
|
* :beginner: Normally follows symbolic link.
|
|
* :gear: Can safely work with broken symbolic link.
|
|
|
|
## Install
|
|
|
|
```console
|
|
npm install @nodelib/fs.stat
|
|
```
|
|
|
|
## Usage
|
|
|
|
```ts
|
|
import * as fsStat from '@nodelib/fs.stat';
|
|
|
|
fsStat.stat('path', (error, stats) => { /* … */ });
|
|
```
|
|
|
|
## API
|
|
|
|
### .stat(path, [optionsOrSettings], callback)
|
|
|
|
Returns an instance of `fs.Stats` class for provided path with standard callback-style.
|
|
|
|
```ts
|
|
fsStat.stat('path', (error, stats) => { /* … */ });
|
|
fsStat.stat('path', {}, (error, stats) => { /* … */ });
|
|
fsStat.stat('path', new fsStat.Settings(), (error, stats) => { /* … */ });
|
|
```
|
|
|
|
### .statSync(path, [optionsOrSettings])
|
|
|
|
Returns an instance of `fs.Stats` class for provided path.
|
|
|
|
```ts
|
|
const stats = fsStat.stat('path');
|
|
const stats = fsStat.stat('path', {});
|
|
const stats = fsStat.stat('path', new fsStat.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`](#options) object or an instance of [`Settings`](#settings) class.
|
|
|
|
> :book: 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.
|
|
|
|
```ts
|
|
const settings = new fsStat.Settings({ followSymbolicLink: false });
|
|
|
|
const stats = fsStat.stat('path', settings);
|
|
```
|
|
|
|
## Options
|
|
|
|
### `followSymbolicLink`
|
|
|
|
* Type: `boolean`
|
|
* Default: `true`
|
|
|
|
Follow symbolic link or not. Call `fs.stat` on symbolic link if `true`.
|
|
|
|
### `markSymbolicLink`
|
|
|
|
* Type: `boolean`
|
|
* Default: `false`
|
|
|
|
Mark symbolic link by setting the return value of `isSymbolicLink` function to always `true` (even after `fs.stat`).
|
|
|
|
> :book: Can be used if you want to know what is hidden behind a symbolic link, but still continue to know that it is a symbolic link.
|
|
|
|
### `throwErrorOnBrokenSymbolicLink`
|
|
|
|
* Type: `boolean`
|
|
* Default: `true`
|
|
|
|
Throw an error when symbolic link is broken if `true` or safely return `lstat` call if `false`.
|
|
|
|
### `fs`
|
|
|
|
* Type: [`FileSystemAdapter`](./src/adapters/fs.ts)
|
|
* 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.
|
|
|
|
```ts
|
|
interface FileSystemAdapter {
|
|
lstat?: typeof fs.lstat;
|
|
stat?: typeof fs.stat;
|
|
lstatSync?: typeof fs.lstatSync;
|
|
statSync?: typeof fs.statSync;
|
|
}
|
|
|
|
const settings = new fsStat.Settings({
|
|
fs: { lstat: fakeLstat }
|
|
});
|
|
```
|
|
|
|
## Changelog
|
|
|
|
See the [Releases section of our GitHub project](https://github.com/nodelib/nodelib/releases) for changelog for each release version.
|
|
|
|
## License
|
|
|
|
This software is released under the terms of the MIT license.
|