naming-format

To enforce consistent file naming in a TypeScript codebase, you can run a repository-wide audit that detects casing inconsistencies like CamelCase versus kebab-case. The tool surfaces violations and provides automated suggestions to standardize file names.

The best way to standardize export naming across mixed-casing modules is to validate suffix-based patterns such as .types.ts and .schema.ts. An audit checks these file suffixes and export naming standards to surface and fix mismatches.

To fix inconsistent kebab-case file names without breaking imports, the tool provides safe rename guidance. It audits index patterns and export names to promote consistent imports and exports across the project during the refactoring process.

Yes, this naming convention audit works specifically for projects with mixed casing and export names. It identifies inconsistencies across files and directories, auditing files, exports, and index patterns to surface violations.

You can automatically apply file suffix conventions like .types.ts across your project by running a repository-wide naming audit. The process validates suffix-based patterns for exports and provides automated guidance to fix any violations found.