Changelog
One entry per release. Full detail in the commit history.
0.1.1 — 2026-08-24
- Fixed a real self-contradiction in the README: the status line said the allowlist covers nine diagnostic codes, "What this does not do" said seven and listed six kinds, omitting wrong-import-form.
- Added a test that extracts every number the README states next to "diagnostic codes" or "finding kinds" and asserts it against the real allowlist, so the two can't drift apart silently again.
0.1.0 — 2026-08-16
- First publish to npm.
- wrong-import-form: TS2614 (a named import against a default-exporting package) and TS1192 (a default import against a package with no default export) both now report as their own kind instead of removed-export — the export exists, the snippet imported it the wrong way.
- Path sanitizer: every finding's message is swept for the CLI's own temp-workspace paths before rendering. If a path survives sanitizing anyway, the finding is dropped rather than shown.
- Fixed the origin gate silently failing on intersection types — the inferred type of a CJS `export =` default import merged with its call signature (e.g. chalk) — which had been dropping real findings on that whole shape of package.
- no-type-declarations: packages that ship no type declarations at all now report that explicitly, instead of a silent zero-findings result indistinguishable from clean docs.
- Fixed two silently-broken diagnostic regexes found by writing one test per allowlisted code: TS2724's message has no "Module " prefix (TS2305's does), and TS2561 reads "Did you mean to write 'x'?", not TS2551's "Did you mean 'x'?". Both had been returning null unconditionally, for every package, since the beginning — with no error, just a finding that never happened.
- Fixed historical/migration content and before/after demonstration snippets being reported as broken — the entire reason a migration guide shows an old API is to demonstrate it's old.