3
0
mirror of https://github.com/larvit/adf-codec.git synced 2026-11-19 14:45:44 +01:00

Answer prose round 1: 0 🔴, 8 🟡 (0 misread); reword the decision, the changelog bullet and the plan sentence, keep contributor text out of the Size row

This commit is contained in:
2026-11-15 13:45:04 +01:00
committed by Lillem4n
parent f78c12cd5f
commit d3832a85b6
4 changed files with 19 additions and 16 deletions
+13 -11
View File
@@ -924,20 +924,22 @@ config gone missing fails the leg instead of falling back to oxlint's own defaul
`--deny-warnings`, since a rule from a category this config never names arrives as a warning it
exits 0 on.
## The published size is a bundler's output, checked within a tenth
## The build ships unminified; the README's size is a minified bundle's, checked within a tenth
2026-11-15, the implementer's recommendation, open to the maintainer. Goal 3. Valid while competitors advertise a minified and gzipped figure.
2026-11-15, the implementer's recommendation, open to the maintainer. Goal 3, and goal 8, which asks a
consumer to configure nothing. Valid while competitors advertise a minified and gzipped figure.
The README states the package's size as what a bundler ships, minified and gzipped, beside the tarball
and the unpacked size, and in a column of the comparison table. That is the figure the other packages
advertise (marklassian's "12kb" measures 13 kB here). `bundle-size/` measures it with esbuild, in its own
package as §Stryker in its own package has it: the bundle of `export * from` the entry, dependencies
included, for Node. The comparison measures every package with the same call.
The README states the package's size as a bundler produces it: the whole package and its dependencies
bundled, minified and gzipped. Competitors advertise that figure (marklassian's "12kb" measures 13 kB
here), so it is the one that compares. `bundle-size/` measures it with esbuild. That package is its own, as
§Stryker in its own package has it, and the comparison table's `converter-comparison/` measures each
package with the same function. The README also states the tarball and the unpacked size.
The build stays tsc's unminified output, since goal 8 asks nothing of a consumer, and a minified build
leaves their debugger and stack traces nothing to read. The gate fails where a README figure is more than
a tenth off the measure: a tighter bound fails most pull requests, and a tenth still catches a feature
that doubles a part of the package. The release job needs the gate, so a stale figure stops a release.
The build stays tsc's unminified output: a consumer has to add no step to read a stack trace or step
through the package in a debugger, and the build takes no minifier. The gate fails where a stated figure
for this package is more than a tenth off the measure. A tighter bound fails most pull requests, while a
tenth still fails a release in which the package has grown by a tenth since its figure was last stated.
The release job needs the gate, so a stale figure stops a release.
## Properties on a fixed seed