Feature: Skip Import Sorting for Specified Files

Problem

In large codebases with hundreds of thousands of files, manually adding // sort-imports-ignore comments to each file that should be excluded from import sorting becomes impractical and maintenance-heavy. This is particularly problematic for:

• Generated files that shouldn't be modified
• Test files with specific import ordering requirements
• Legacy code that should maintain its current import structure
• Specific directories that should be excluded from import sorting

Solution

This PR introduces a new configuration option importOrderSkipFiles that allows users to specify glob patterns for files that should be excluded from import sorting. This provides a more scalable and maintainable way to manage import sorting exclusions.

New Configuration Option

{
 "importOrderSkipFiles": [
 "generated/**", // Skip all files in generated directory
 "*.test.{ts,tsx}", // Skip all test files
 "legacy/*.js", // Skip specific directory
 "specific-file.ts" // Skip specific file
 ]
}

Features

• 🎯 Pattern-based file matching using minimatch
• 📁 Supports both directory and file patterns
• 🔄 Works with relative and absolute paths
• ⚡ Efficient pattern matching for large codebases
• 🧪 Comprehensive test coverage

Implementation Details

• Added minimatch dependency for robust glob pattern matching
• Implemented shouldSkipFile utility with thorough test coverage
• Integrated skip functionality in the main preprocessor
• Added TypeScript types for the new configuration option

Testing

The implementation includes comprehensive tests covering:

• Empty skip patterns
• Various glob pattern scenarios
• Directory-specific patterns
• Filename-only patterns
• Special character handling
• Mixed path separator support
• Exact filename matches

Usage Example

{
 "importOrder": ["^@core/(.*)$", "^@server/(.*)$", "^@ui/(.*)$", "^[./]"],
 "importOrderSkipFiles": [
 "generated/**/*.ts",
 "**/*.test.{ts,tsx}",
 "legacy/**"
 ]
}

Breaking Changes

None. This is a purely additive feature that maintains backward compatibility.

Future Considerations

• Add support for negative patterns (e.g., !generated/important.ts)
• Consider adding directory-specific import ordering rules
• Add documentation for common skip patterns and use cases