Sample

Verify that @babel/core ignores .babelrc configuration when filename is omitted

sha256:27a75309583baf4bc1a621d90c86e0128d56648e2a829150c83c08ca79c054b8

Case

Goal

Verify that @babel/core ignores .babelrc configuration when filename is omitted HOW

Packages

@babel/core 8.0.1

Environment

node

Created

2026-08-17T01:44:22Z

Commonly assumed

babel.transformSync automatically discovers and loads .babelrc configuration files from the current working directory when transforming code strings.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• babel.transformSync and babel.loadPartialConfigSync ignore .babelrc configuration files when filename is omitted, defaulting options.babelrc to false
• loadPartialConfigSync without filename returns hasFilesystemConfig false and leaves babelrc undefined
• transformSync with babelrc true still fails to resolve .babelrc without a filename
• transformSync with filename resolves .babelrc.json and applies configured transformations

Files

• .babelrc.json
• NOTES.md
• 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

csx-seed

Verification receipts

• node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9