State the shipped ECMAScript floor in engines, not the toolchain's

2026-09-01 16:51:15 +02:00
parent 1b7f66546e
commit 082dabb261
3 changed files with 4 additions and 4 deletions
@@ -65,7 +65,8 @@ they never reach a consumer.
  `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
  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.
 - 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`),