tselect-npm / thrown / 33311061305

100%

push

github

:boom: Modernize toolchain: pnpm, tsdown, Vitest, Biome, TypeScript 7, CI

Ten concerns, one commit — this repository's ruleset allows squash merges only,
so the gitmoji series from `chore/modernize` is recorded here rather than replayed
onto `main`:

  :bug:              Stop shipping repo cruft in the published package
  :wrench:           Migrate to pnpm
  :sparkles:         Add dual ESM + CJS build via tsdown
  :white_check_mark: Migrate test suite to Vitest
  :white_check_mark: Cover the three untested branches
  :rotating_light:   Replace implicit lint-free-ness with Biome
  :arrow_up:         Upgrade TypeScript to 7.0.2
  :memo:             Restructure the README and complete package metadata
  :construction_worker: Run CI from the org-wide reusable workflow
  :construction_worker: Add the release caller workflow

`:boom:` rather than the branch's `:wrench:` because a squash leaves one commit to
infer the bump from, and `:wrench:` infers as no release at all. The `bump: major`
override is still the documented way to ship this, but the history now says so on
its own instead of depending on whoever runs the workflow remembering to.

The major is forced twice over:

  - `engines.node` is now `>=22`, the bottom of the CI matrix.
  - The public API moves from `any` to `unknown` (`Err extends Object` becomes
    `extends object`), which Biome flagged. A compile-time break for consumers
    relying on `any` to skip narrowing; runtime behaviour is unchanged.

No runtime behaviour changed. The source diff is entirely type-level, and that was
verified rather than argued: 144 scenarios across the whole API run against the
published 1.0.2 and against both new entry points produced identical transcripts —
288 comparisons, 0 mismatches. Every README example typechecks under `strict` +
`nodenext` and prints what it documents.

Headline fix: 1.0.2 shipped `.idea/`, `.mocharc.json`, both tsconfigs and a stray
2.9 MB `.log30912` — invisible to `git status`, ship... (continued)

14 of 14 branches covered (100.0%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

17 of 17 relevant lines covered (100.0%)

5.82 hits per line