Grasp
Public
Showcasedate-fns/date-fns #4198SourceMarkdown

Introduce `@date-fns/cdn`, deprecate CDN served from `date-fns`

This PR addresses part of the problem with the date-fns package becoming way too large:

MERGEDGrasp · Jul 30, 2026

Three explanations of the same brief

No jargon, about fifteen seconds

Introduce `@date-fns/cdn`, deprecate CDN served from `date-fns`

Someone changed how a program works. This PR addresses part of the problem with the date-fns package becoming way too large: The part to watch: Configuration changed.

Introduce `@date-fns/cdn`, …Heaviest file
The one thing to take away

27 words · derived from the brief below, no model involved

The change is spread across 30 files in 5 areas, with no single file dominating.

30 files changed across 5 areas of date-fns/date-fns, 591 added and 194 removed.

This PR addresses part of the problem with the date-fns package becoming way too large:

heaviestdate-fns30 files, 785 linesBuild & CI4 files, 346 linesSource11 files, 237 linesConfig11 files, 123 linesDocs2 files, 61 linesTests2 files, 18 linescdn.ts+157 −72
Where the change landed. Node size is not to scale; the line counts are exact.Download for draw.io
Heaviest file

pkgs/core/scripts/build/cdn.ts, +157 −72, which is 29% of the change.

Tests moved with it

2 test files changed alongside 11 source files.

Configuration touched

mise.toml, pnpm-lock.yaml, package.json. Config changes are small in the diff and large in effect.

Spread

30 files, 785 changed lines in total.

What this brief could not check

  • No language model read this change. Every statement here is computed from file paths, line counts, and CI status, so it describes the shape of the diff and not what the diff means.
  • 4 patch(es) were not retrieved, so any file among them is described by its stat line only.