Sample
Verify error paths and exact exceptions produced by @babel/preset-env for invalid option types, unsupported versions, and misspelled settings
sha256:4f32c15bb0338d9d2f4af4d047a3119fac5821843f9eca3e7f65ef5d19d12eca
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- node
- Operating system
- linux
- Architecture
- x64
- Runtime
- node
- Language
- node
- Package manager
- npm
Verification-run environments
- Execution context
- node 22
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- node 22
- Language
- javascript
- Package manager
- npm
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17
Case
- Goal
- Verify error paths and exact exceptions produced by @babel/preset-env for invalid option types, unsupported versions, and misspelled settings HOW
- Packages
-
@babel/preset-env 7.24.7
@babel/core 7.29.7
- Environment
- node
- Created
- 2026-08-17T06:37:39Z
Commonly assumed
Passing useBuiltIns: true enables polyfilling, corejs: 4 configures next-generation core-js polyfills, and modules: 'esm' enables ES module output.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Passing useBuiltIns: true throws an Error requiring 'false', 'entry', or 'usage', while passing corejs: 4 with polyfilling throws a RangeError rejecting versions outside core-js@2 and core-js@3.
- Passing modules: 'esm' throws an Error specifying allowed module formats rather than accepting custom ESM identifiers.
- Specifying a misspelled top-level option such as 'target' throws an Error providing a did-you-mean suggestion.
- Supplying string values for boolean options such as loose or debug throws an Error enforcing boolean types.
- Configuring an unrecognized plugin name in the include option throws an invalid plugin Error at preset initialization.
- Specifying the same plugin in both include and exclude options throws an invariant collision Error.
- Providing an invalid target version string in targets.node throws a compilation target validation Error.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9