网络测出了什么
下面每一行都是测量结果，不是观点。每一条都链接到一个已发布的样本，其 contract 在断网的固定容器中执行，你可以自己重跑并反驳结论。
操作系统和运行时来自所链接样本记录的环境；缺少该维度的条目会在筛选时排除。
597 条发现，覆盖 8 个生态。
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
样本自述，其契约实测
正在显示已发布样本测得的第 1–25 条(共 568 条)。
-
pypi样本契约python · linux 24/x64cffi@2.1.1
普遍认为Calling ffi.string with maxlen reads the full byte length regardless of null bytes, and ffi.buffer on a pointer defaults to the full allocated buffer length.
实测Calling ffi.string(cdata, maxlen) truncates at the first null byte rather than reading maxlen bytes, while ffi.unpack extracts the exact byte count across embedded nulls.
-
npm样本契约node · linux 24/x64browserslist@4.28.7
普遍认为Modifying .browserslistrc on disk causes browserslist to automatically pick up the updated target configuration on subsequent queries in a long-running process.
实测When .browserslistrc is modified on disk during a process lifetime, browserslist continues to return stale cached configurations until browserslist.clearCaches() is explicitly invoked.
-
npm样本契约node 22.23 · linux 24/x64@babel/preset-env@7.26.9
普遍认为Modern compilation targets automatically negate all transforms regardless of configuration options like forceAllTransforms, and preset-level settings like bugfixes or loose are not systematically passed to configured plugins.
实测presetEnv with forceAllTransforms: true forces all 49 syntax transform plugins to activate even when targeting modern Chrome 120 (which normally requires 17).
-
npm样本契约node 22.23 · linux 24/x64@rollup/plugin-commonjs@28.0.2
普遍认为When bundling CommonJS modules that require external dependencies into ESM, @rollup/plugin-commonjs automatically imports them as ES module namespaces or detects external module formats to preserve named exports.
实测By default, @rollup/plugin-commonjs renders external dependencies required in CommonJS modules as default ESM imports rather than namespace imports.
-
npm样本契约node 22.23 · linux 24/x64@rollup/plugin-commonjs@28.0.2
普遍认为When bundling CommonJS modules that wrap external require calls inside try-catch blocks into ESM, @rollup/plugin-commonjs always hoists the requires to top-level static imports or always preserves runtime try-catch error handling.
实测By default, @rollup/plugin-commonjs leaves external require calls inside try-catch blocks untransformed as dynamic require() calls, preventing top-level static ESM imports.
-
npm样本契约node · linux 24/x64@rollup/plugin-commonjs@28.0.2
普遍认为When bundling CommonJS modules containing dynamic require calls, @rollup/plugin-commonjs resolves dynamic calls automatically or leaves them untouched without requiring explicit configuration.
实测By default, @rollup/plugin-commonjs transforms dynamic require calls into commonjsRequire helper calls that throw an error instructing the user to configure dynamicRequireTargets or ignoreDynamicRequires.
-
npm样本契约node 22.23 · linux 24/x64@rollup/plugin-commonjs@29.0.3
普遍认为When bundling CommonJS modules with dynamic require expressions, @rollup/plugin-commonjs either automatically resolves dynamic calls at runtime or silently ignores them without error.
实测By default, @rollup/plugin-commonjs transforms dynamic require calls into commonjsRequire helper calls that throw an error instructing the user to configure dynamicRequireTargets or ignoreDynamicRequires.
-
npm样本契约node 22.23 · linux 24/x64@rollup/plugin-commonjs@29.0.3
普遍认为When bundling CommonJS modules that wrap external require calls inside try-catch blocks into ESM, @rollup/plugin-commonjs always hoists the requires to top-level static imports or always preserves runtime try-catch error handling.
实测By default, @rollup/plugin-commonjs leaves external require calls inside try-catch blocks untransformed as dynamic require() calls, preventing top-level static ESM imports.
-
npm样本契约node 22.23 · linux 24/x64@rollup/plugin-commonjs@29.0.3
普遍认为When bundling CommonJS modules that require external dependencies into ESM, @rollup/plugin-commonjs automatically imports them as ES module namespaces or detects external module formats to preserve named exports.
实测By default, @rollup/plugin-commonjs renders external dependencies required in CommonJS modules as default ESM imports rather than namespace imports.
-
npm样本契约node · linux 24/x64@babel/preset-env@7.26.9
普遍认为Developers expect specifying useBuiltIns alone without corejs to automatically configure polyfill plugins, or expect getPolyfillPlugins to return non-empty default plugins even when useBuiltIns is false or unset.
实测getPolyfillPlugins returns an empty array when useBuiltIns is unset, false, or not usage/entry, or when corejs is missing.
-
npm样本契约linux 24/x64@rollup/plugin-commonjs@28.0.7
普遍认为Bundling CommonJS code with Rollup leaves dynamic require calls as native runtime require invocations in the output bundle.
实测assert @rollup/plugin-commonjs with default ignoreDynamicRequires (false) rewrites dynamic require calls into commonjsRequire helper that throws a runtime error
-
npm样本契约node 22.23 · linux 24/x64@babel/preset-env@7.26.9
普遍认为Modern compilation targets automatically negate all transforms regardless of configuration options like forceAllTransforms, and preset-level settings like bugfixes or shippedProposals do not alter plugin resolution counts for modern environments.
实测presetEnv with forceAllTransforms: true forces all 49 syntax transform plugins to activate even when targeting modern Chrome 120 (which normally requires 17).
-
npm样本契约node 22.23 · linux 24/x64@babel/preset-env@8.0.2
普遍认为Compilation targets strictly dictate plugin selection, requiring full package names if manually overridden, and include and exclude silently resolve collisions by precedence rather than throwing an error.
实测Configuring the include option with transform-arrow-functions forces transpilation of arrow functions to function expressions even when targeting modern runtimes (such as Chrome 120) that natively support them, while preserving non-included syntax like template literals.
-
npm样本契约node 22.23 · linux 24/x64@babel/preset-env@8.0.2
普遍认为Modern compilation targets like Chrome 120 prevent all syntax transformations, forceAllTransforms converts ES module syntax into CommonJS require calls, and exclude is ignored when forceAllTransforms is true.
实测When forceAllTransforms is omitted or false, @babel/preset-env preserves native modern syntax (arrow functions, template literals, optional chaining) for targets that natively support them.
-
npm样本契约node 22.23 · linux 24/x64@rollup/plugin-commonjs@28.0.7
普遍认为By default @rollup/plugin-commonjs hoists all CommonJS require calls including those inside try-catch blocks into top-level static imports.
实测assert @rollup/plugin-commonjs by default (ignoreTryCatch: true) leaves external require calls inside try-catch blocks unconverted as runtime require statements without hoisting static imports
-
npm样本契约node 22.23 · linux 24/x64@babel/preset-env@7.26.0
普遍认为Configuring polyfill injection with useBuiltIns 'usage' or 'entry' generates identical plugin lists, and legacy polyfill handling is only applied when corejs version 2 is specified.
实测assert useBuiltIns 'usage' with corejs 3 selects pluginCoreJS3 with method 'usage-global' and legacyBabelPolyfillPlugin marked as deprecated
-
npm样本契约node · linux 24/x64@babel/preset-env@7.26.0
普遍认为Disabling module transforms in @babel/preset-env removes all module-related plugins entirely, and requesting dynamic import transformation enables transform-dynamic-import across all formats including UMD.
实测assert modules: 'commonjs' with shouldTransformESM maps the module format to its transformation plugin alongside dynamic import and export-namespace transforms
-
npm样本契约node · linux 24/x64@rollup/plugin-commonjs@28.0.7
普遍认为By default @rollup/plugin-commonjs allows CommonJS modules requiring external ES modules to access both default and named exports.
实测assert @rollup/plugin-commonjs with default esmExternals: false emits default imports for external dependencies, causing named exports to be inaccessible (undefined) when required from CommonJS
-
npm样本契约node 22.23 · linux 24/x64@babel/preset-env@7.29.7
普遍认为Modern compilation targets automatically negate all transforms regardless of configuration options like forceAllTransforms, and preset-level settings like bugfixes or loose are not systematically passed to configured plugins.
实测presetEnv with forceAllTransforms: true forces all 50 syntax transform plugins to activate even when targeting modern Chrome 120 (which normally requires 18).
-
npm样本契约node · linux 24/x64@babel/preset-env@7.26.0
普遍认为Targeting a modern environment like Node 20 prevents syntax transforms like arrow functions from running, and targeting older environments compiles all modern syntax without granular options to selectively force or skip specific transforms.
实测assert include with shorthand 'transform-arrow-functions' forces arrow function compilation on targets that natively support them such as node 20
-
npm样本契约node 22 · linux 24/x64@babel/preset-env@7.29.7
普遍认为Target-based compilation dynamically configures the plugin pipeline, and preset helper utilities resolve feature requirements and partition syntax transforms.
实测isPluginRequired returns true when target version is below support requirement, and false when target meets or exceeds requirement.
-
npm样本契约node 22 · linux 24/x64@babel/preset-env@7.24.7
普遍认为Target-based compilation dynamically configures the plugin pipeline, and preset helper utilities resolve feature requirements and partition syntax transforms.
实测isPluginRequired returns true when target version is below support requirement, and false when target meets or exceeds requirement.
-
golang样本契约go · linux/x64google.golang.org/protobuf@v1.35.1
普遍认为reflect.DeepEqual safely compares protobuf messages while proto.Equal behaves identically to standard struct comparisons.
实测proto.Equal returns true when comparing two nil proto.Message values, and returns false when comparing a non-nil message with nil.
-
pypi样本契约python · linux/x64pydantic@2.13.4
普遍认为Pydantic field_validators always receive raw uncoerced input by default and can access all sibling fields in ValidationInfo.data regardless of field definition order.
实测Leaving field_validator mode unset defaults to 'after', running after core type coercion; inputs that fail core type coercion raise ValidationError before the after-validator executes.
-
npm样本契约node 22.23 · linux 24/x64socket.io-client@4.8.1
普遍认为Emitted events are always intercepted immediately by onAnyOutgoing regardless of connection state, volatile.emit queues offline packets like standard emit, and emitWithAck resolves directly without handling socket.io error-first ack protocol or timeout errors.
实测assert volatile emit while disconnected discards event immediately without queuing in sendBuffer whereas regular emit is queued
如何核对这里的任何一行
打开样本，读它的 contract，然后运行。contract 就是该样本自己的测试：它在断网的固定容器中运行，那次运行的签名回执才是网络所存储的东西。这里没有一条依赖我们对某个库的理解，只依赖这个库实际做了什么。
有些已发布的样例不在这个页面上。它们的契约通过了，样例也是活的 —— 但契约里没有一行能当句子读。像 expect(x).toBe(1) 这样的断言，放在它所检验的那个认知旁边，对读者什么也没说。与其登出没人能读的证据，不如空着。