v0.1.8

New: tsconfig customConditions are honored during resolution

If your tsconfig sets compilerOptions.customConditions, ImportLint now applies those conditions when matching conditional package.json exports and #-subpath imports entries — so resolution agrees with what tsc and a bundler configured with the same conditions see. Previously the resolver only matched the fixed set types/import/require/node (plus default), so an imports map gated on a custom condition — like Vite lib-mode's #src/* mapping sources under a project-specific condition (#4) — fell through to its default branch or failed to resolve entirely, and those imports were silently skipped (or flagged by --report-unresolved) instead of being checked.

The conditions are read from the same tsconfig that already feeds the resolver (config tsconfig, --tsconfig, or the auto-discovered <project root>/tsconfig.json), with TypeScript's own semantics: extends chains are followed (including TS 5.0 array extends and bare-package targets resolved through node_modules), and customConditions is a non-merged option — the nearest definition wins. Watch mode picks up tsconfig edits automatically, as before.

Lint behavior is unchanged for projects whose tsconfig sets no customConditions — checking and output are identical to v0.1.7.

Full Changelog: v0.1.7...v0.1.8