larvit/adf-codec
3
0
Fork 0
Code Pull Requests 1 Actions Activity

Hold the shipped source to ECMAScript alone, and run the suite on Deno and Bun #39

Merged
lilleman merged 6 commits from runs-anywhere into main 2026-09-01 17:18:07 +02:00
Conversation 0 Commits 6 Files Changed 8
+4 -4
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 082dabb261 - Show all commits
AGENTS.md
+2 -1
View File
@@ -65,7 +65,8 @@ they never reach a consumer.
`tsconfig.build.json` is that gate, typechecking the shipped files alone with `types: []` and `tsconfig.build.json` is that gate, typechecking the shipped files alone with `types: []` and
`lib: ES2022`, so `node:fs`, `process` and an ES2024 method are compile errors here rather than a `lib: ES2022`, so `node:fs`, `process` and an ES2024 method are compile errors here rather than a
consumer's crash there. Node's test runner, the corpus reads and the build are the repo's own, consumer's crash there. Node's test runner, the corpus reads and the build are the repo's own,
never the library's. never the library's, and `engines.node` states the floor the shipped JavaScript needs — `>=18`,
the lowest line carrying ES2022 — never the higher one those repo-only tools want.
- ESM only — no CommonJS build, no dual-package hazard. - ESM only — no CommonJS build, no dual-package hazard.
- One entrypoint: built JavaScript, `.d.ts` beside it. Do not add a TypeScript-source entrypoint — - One entrypoint: built JavaScript, `.d.ts` beside it. Do not add a TypeScript-source entrypoint —
Node refuses to type-strip under `node_modules` (`ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING`), Node refuses to type-strip under `node_modules` (`ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING`),
package.json
+1 -1
View File
@@ -10,7 +10,7 @@
}, },
"type": "module", "type": "module",
"engines": { "engines": {
"node": ">=24" "node": ">=18"
}, },
"scripts": { "scripts": {
"test": "node --test --experimental-test-coverage --test-coverage-exclude=\"src/**/*.test.ts\" --test-coverage-branches=97 --test-coverage-functions=100 --test-coverage-lines=100 \"src/**/*.test.ts\"", "test": "node --test --experimental-test-coverage --test-coverage-exclude=\"src/**/*.test.ts\" --test-coverage-branches=97 --test-coverage-functions=100 --test-coverage-lines=100 \"src/**/*.test.ts\"",
todo.md
+1 -2
View File
@@ -145,8 +145,7 @@ numbering is the order the work was planned in, not the order it ships.
maintainer's bump PR also removes `private: true`, the guard against any earlier publish. maintainer's bump PR also removes `private: true`, the guard against any earlier publish.
§6's browser half is first checkable here, on the emitted `dist/index.js` a browser can §6's browser half is first checkable here, on the emitted `dist/index.js` a browser can
load — the compile gate names no host API, and a real page converting a document is the load — the compile gate names no host API, and a real page converting a document is the
other half. `engines` is settled here too: `>=24` is the toolchain's floor, not the ES2022 other half.
one the shipped JavaScript needs, and it reads to a consumer as the latter.
**Settled** (the maintainer, 2026-09-01): the round-trip proved over the checked-in corpus **Settled** (the maintainer, 2026-09-01): the round-trip proved over the checked-in corpus
is what `0.1.0` ships on, and the open-ended proof work follows it rather than gating it — is what `0.1.0` ships on, and the open-ended proof work follows it rather than gating it —
3k's spec suite and 4's generators and maintainer-supplied payloads are `0.2.0`, 4b's retry 3k's spec suite and 4's generators and maintainer-supplied payloads are `0.2.0`, 4b's retry