work in progress

gendn

Generated reference docs for the APIs that ship in Chrome but don't yet have a page on MDN. When MDN already covers an API, gendn just links out. The goal is the gap between "shipped in Chrome" and "documented on developer.mozilla.org".

Last updated 25d ago (14 Oct, 03:48 UTC) · commit 393f905

releases

  1. Chrome 160 Dev Stable date: 5 Jan 2027
  2. Chrome 159 Beta Stable date: 8 Dec 2026
  3. Chrome 158 Stable (rolling out) Stable date: 17 Nov 2026
  4. Chrome 157 Stable (live) Most users are here
  5. Chrome 154 Archive Backfilled
  6. Chrome 153 Archive Backfilled
  7. Chrome 152 Archive Backfilled
  8. Chrome 151 Archive Backfilled
  9. Chrome 150 Archive Backfilled
  10. Chrome 149 Archive Backfilled
  11. Chrome 148 Archive Backfilled
  12. Chrome 147 Archive Backfilled

Or jump straight to the full API catalogue to search across every release at once.

how it works

  1. A daily routine reads chromestatus.com for features shipping in Chrome (stable, beta, dev, plus prev-stable).
  2. For each, it checks MDN. If MDN has a page, gendn just links to MDN.
  3. If MDN doesn't have a page, the routine writes a reference doc generated from the spec, explainer, and the IDL in Chromium source.
  4. When MDN later ships its own page, the routine notices on the next pass and the gendn entry switches to a "see MDN" stub.

Sister project: chrome-platform-showcase — interactive demos for the same set of features. Repo: PaulKinlan/gendn.