path-alias-validator

To validate path aliases in configuration files, scan tsconfig.json, vitest.config.ts, tsup.config.ts, and package.json to ensure alias mappings remain consistent. This prevents mismatched path configurations across your build and test environments.

To validate path aliases in configuration files, scan tsconfig.json, vitest.config.ts, tsup.config.ts, and package.json to ensure alias mappings remain consistent. This prevents mismatched path configurations across your build and test environments.

Yes, you can fix inconsistent path alias usage in documentation code blocks. The validator detects relative imports that require replacement and suggests automated fixes to align documentation examples with your alias configuration.

The best way to enforce consistent import paths and refactor JavaScript code is to run an automated validation tool. It detects non-aliased imports and proposes refactoring replacements to improve overall maintainability.