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>
3.3 KiB
3.3 KiB
import/no-unused-modules
Reports:
- modules without any exports
- individual exports not being statically
imported orrequireed from other modules in the same project - dynamic imports are supported if argument is a literal string
Rule Details
Usage
In order for this plugin to work, at least one of the options missingExports or unusedExports must be enabled (see "Options" section below). In the future, these options will be enabled by default (see https://github.com/import-js/eslint-plugin-import/issues/1324)
Example:
"rules": {
...otherRules,
"import/no-unused-modules": [1, {"unusedExports": true}]
}
Options
This rule takes the following option:
missingExports: iftrue, files without any exports are reported (defaults tofalse)unusedExports: iftrue, exports without any static usage within other modules are reported (defaults tofalse)ignoreUnusedTypeExports: iftrue, TypeScript type exports without any static usage within other modules are reported (defaults tofalseand has no effect unlessunusedExportsistrue)src: an array with files/paths to be analyzed. It only applies to unused exports. Defaults toprocess.cwd(), if not providedignoreExports: an array with files/paths for which unused exports will not be reported (e.g module entry points in a published package)
Example for missing exports
The following will be reported
const class MyClass { /*...*/ }
function makeClass() { return new MyClass(...arguments) }
The following will not be reported
export default function () { /*...*/ }
export const foo = function () { /*...*/ }
export { foo, bar }
export { foo as bar }
Example for unused exports
given file-f:
import { e } from 'file-a'
import { f } from 'file-b'
import * as fileC from 'file-c'
export { default, i0 } from 'file-d' // both will be reported
export const j = 99 // will be reported
and file-d:
export const i0 = 9 // will not be reported
export const i1 = 9 // will be reported
export default () => {} // will not be reported
and file-c:
export const h = 8 // will not be reported
export default () => {} // will be reported, as export * only considers named exports and ignores default exports
and file-b:
import two, { b, c, doAnything } from 'file-a'
export const f = 6 // will not be reported
and file-a:
const b = 2
const c = 3
const d = 4
export const a = 1 // will be reported
export { b, c } // will not be reported
export { d as e } // will not be reported
export function doAnything() {
// some code
} // will not be reported
export default 5 // will not be reported
Unused exports with ignoreUnusedTypeExports set to true
The following will not be reported:
export type Foo = {}; // will not be reported
export interface Foo = {}; // will not be reported
export enum Foo {}; // will not be reported
Important Note
Exports from files listed as a main file (main, browser, or bin fields in package.json) will be ignored by default. This only applies if the package.json is not set to private: true
When not to use
If you don't mind having unused files or dead code within your codebase, you can disable this rule