Skip to content

docs(core): refresh stale figures in README#294

Merged
TylerVigario merged 2 commits into
mainfrom
docs/refresh-readme-numbers
May 9, 2026
Merged

docs(core): refresh stale figures in README#294
TylerVigario merged 2 commits into
mainfrom
docs/refresh-readme-numbers

Conversation

@TylerVigario
Copy link
Copy Markdown
Collaborator

@TylerVigario TylerVigario commented May 8, 2026

Summary

Three places carried stale or mismatched figures for the same underlying metric:

File Was Now
README.md "~2.4 KB gzipped per language" (×2) "~2 KB"
README.md "~87% global coverage" "any browser with BigInt support"
.browserslistrc:12 "~87% of global users" prose pointing at npx browserslist --coverage
rollup.config.js:58 "~85.9% global coverage" prose, no number

Reality check: average gzipped per-language ESM bundle is 2.2 KB across the 72 languages (range 1.7–2.9 KB), and the current caniuse coverage for defaults and supports bigint is ~85.5%. The three files all cited different numbers (87 / 87 / 85.9), so even before the caniuse drift they weren't internally consistent.

Replacing the precise figures with rough phrasing means the next caniuse market-share shift doesn't restale anything.

Spot-checks confirmed the rest of the README is accurate: 72 language files (matches "70+"), every language exports all three forms, UMD shape (n2words.enUS, .ordinal.enUS, .currency.enUS) matches rollup.config.js, browser version baselines (Chrome 67+ / FF 68+ / Safari 14+ / Edge 79+) are correct for BigInt support, Node.js 22+ matches engines.node.

Test plan

  • markdownlint-cli2 README.md passes
  • npx browserslist --coverage still resolves correctly (config unchanged, only comment edited)
  • No links broken

The "~2.4 KB gzipped" claim and "~87% global coverage" figure both
drifted out of sync with reality:

- Average gzipped per-language ESM bundle is now ~2.2 KB across the
  72 languages (range 1.7-2.9 KB).
- caniuse data for `defaults and supports bigint` is now ~85.5%, no
  longer ~87%.

Replace both with rough phrasing ("~2 KB", "any browser with BigInt
support") so future caniuse drift doesn't restale the docs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@TylerVigario TylerVigario requested a review from forzagreen as a code owner May 8, 2026 03:26
Same drift fix as the README change: .browserslistrc cited "~87%"
and rollup.config.js cited "~85.9%" — both stale, and they didn't
even agree with each other. Replace both with prose that points
readers to `npx browserslist --coverage` if they want the current
number.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@TylerVigario TylerVigario merged commit 1dec42d into main May 9, 2026
7 checks passed
@TylerVigario TylerVigario deleted the docs/refresh-readme-numbers branch May 9, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant