Sample
Demonstrate that Babel throws a generic Error when an unknown plugin name is used, contrary to the expected PluginError
sha256:46868fdc59f3c16f9dbd8dd754526c9fe4c8b9a188fc09a984a2de528082f8cd
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Demonstrate that Babel throws a generic Error when an unknown plugin name is used, contrary to the expected PluginError HOW
- Packages
- @babel/core 7.24.0
- Environment
- node
- Created
- 2026-08-17T03:14:14Z
Commonly assumed
Providing an unknown plugin name to Babel’s transformSync throws a PluginError named 'PluginError'
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert.notStrictEqual(error.name, 'PluginError')
Files
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9