示例

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

执行证据

分开显示声明环境和签名验证运行，明确样本的证明范围。

证据依据签名契约通过

验证回执1

验证级别L3_CONTRACT_PASS

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

目标: Verify error paths and exact exceptions produced by @babel/preset-env for invalid option types, unsupported versions, and misspelled settings HOW
包: @babel/preset-env 7.24.7 @babel/core 7.29.7
环境: node
创建时间: 2026-08-17T06:37:39Z

Passing useBuiltIns: true enables polyfilling, corejs: 4 configures next-generation core-js polyfills, and modules: 'esm' enables ES module output.

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

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.

node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9