ネットワークが見つけたもの
以下の各行は意見ではなく測定です。いずれも公開サンプルにリンクしており、その contract はネットワークを切った固定コンテナで実行されるので、自分で再実行して結果に反論できます。
OS とランタイムはリンク先サンプルに記録された環境です。その項目がない記録は選択時に除外されます。
597 件の発見、8 個のエコシステム。
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
サンプルが述べ、その契約が測ったこと
公開サンプルが測定した結果の 251–275 件目(全 568 件)。
-
npmサンプル契約node · linux/x64happy-dom@20.11.2
信じられていることA competent reader expects that omitting script-evaluation settings in happy-dom still evaluates inline `<script>` blocks like a browser would.
測定結果In happy-dom 20.11.2, constructing `Window` without `settings.enableJavaScriptEvaluation` means inline script execution is disabled, so a script that sets `window.__ran = true` leaves `window.__ran` undefined.
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることA strong implementation instinct is that `jest.setSystemTime` accepts any date-like input, including ISO strings, when using fake timers.
測定結果Calling `jest.setSystemTime` with an ISO string under fake timers throws; it only accepts a `Date` object or a numeric epoch timestamp.
-
npmサンプル契約node · linux/x64express@4.19.1
信じられていることA seasoned developer expects `app.configure(...)` to remain available in Express 4 as it did in v3.
測定結果In Express 4.19.1, `app.configure` is undefined and calling `app.configure(...)` throws `TypeError`, showing the v3-style helper no longer exists.
-
npmサンプル契約node · linux/x64es-toolkit@1.49.0
信じられていることMost callers assume the second argument of `chunk` defaults to 1 when omitted.
測定結果Calling `chunk([1, 2, 3])` must throw a runtime error because `size` is required.
-
npmサンプル契約node · linux/x64express@4.19.1
信じられていることForwarded client IP headers should always be reflected in `req.ip` even when `trust proxy` is disabled.
測定結果A request to `/ip` without `trust proxy` ignores `X-Forwarded-For` and `req.ip` is not the forwarded client value.
-
npmサンプル契約node · linux/x64commander@10.0.0
信じられていることA leading space before a positional signature is ignored by Commander, so `program.arguments(' <name>')` is equivalent to `program.arguments('<name>')`.
測定結果In Commander 10, a leading-space argument signature is not ignored, so parsing `['node', 'app', 'only']` with `new Command().arguments(' <required> [optional]')` throws `commander.missingArgument` and does not accept a single positional argument.
-
npmサンプル契約node · linux/x64commander@15.0.0
信じられていることWhen both `--cache` and `--no-cache` are defined, omitting both options should leave `cache` as `true` because the negated form implies a true default.
測定結果With both `--cache` and `--no-cache`, parsing without either flag leaves `program.opts().cache` as `undefined`, even though the negated option alone would default to true.
-
npmサンプル契約node · linux/x64bun@1.3.14
信じられていることCalling server.stop() on a Bun.serve HTTP server terminates all active client connections and immediately frees server resources.
測定結果assert server.pendingRequests is 1 while an in-flight request is being processed by the fetch handler
-
npmサンプル契約node · linux/x64chalk@6.0.0
信じられていることA caller should get the same kind of rejection for all obviously malformed `chalk.hex(...)` inputs.
測定結果`chalk.hex('')('x')` also returns black 24-bit ANSI output instead of an error.
-
npmサンプル契約node · linux/x64bun@1.3.14
信じられていることBun.password.verify returns false whenever a candidate password fails to verify against an unparseable, legacy, or corrupted hash string.
測定結果Bun.password.verify throws an Error with code PASSWORD_UNSUPPORTED_ALGORITHM for arbitrary non-empty hash strings and PASSWORD_INVALID_ENCODING for malformed prefixes rather than returning false, while an empty string hash returns false.
-
npmサンプル契約node · linux/x64@babel/preset-env@8.0.2
信じられていることA shared preset-env tuple can be safely mutated between runs so each transform picks up the latest target value.
測定結果Calling transformAsync twice with the same preset tuple and then changing `targets` in between does not recompute the tuple for the second run.
-
npmサンプル契約node 22.18 · linux/x64@babel/core@8.0.1
信じられていることBecause @babel/core 8 ships as ESM, `require('@babel/core')` must always throw ERR_REQUIRE_ESM.
測定結果CommonJS require and ESM import expose the same transformSync function.
-
golangサンプル契約go 1.26 · linux/x64github.com/gin-gonic/gin@v1.12.0
信じられていることAbortWithStatusJSON immediately returns from the current handler, so code after it cannot run and an explicit return is unnecessary.
測定結果assert binding an empty required name with ShouldBindJSON lets the handler choose HTTP 422 and a JSON error response
-
npmサンプル契約node · linux/x64@babel/core@8.0.1
信じられていることBecause Babel 8 presents an ES module API, `require('@babel/core')` throws `ERR_REQUIRE_ESM` and only dynamic `import()` can reach `transformSync`.
測定結果In @babel/core 8.0.1, `require('@babel/core')` returns an API object whose `transformSync` member is a function.
-
npmサンプル契約node · linux/x64@babel/core@7.29.6
信じられていることA model would likely expect Babel to treat `new super()` like a standard callable super-expression form and return transpiled output instead of throwing.
測定結果`transformSync` does not return transformed code for `class A extends class {} { constructor() { new super() } }`; it throws a syntax error for this invalid `new super()` form.
-
pubサンプル契約dart · linux/x64collection@1.18.0
信じられていることIterableExtension.sample provides a randomly ordered subset of elements, meaning that requesting a sample equal to the collection's size will return a shuffled permutation.
測定結果Before 1.19.0, calling sample() on an iterable requesting its full length returns the elements in their exact original order, rather than a randomly shuffled permutation.
-
gemサンプル契約ruby · linux/x64zeitwerk@2.6.0
信じられていることZeitwerk silently skips a file that defines a different constant than its path implies
測定結果Accessing Foo when lib/foo.rb defines Bar raises Zeitwerk::NameError and the error identifies the missing expected constant Foo.
-
gemサンプル契約ruby · linux/x64zeitwerk@2.8.3
信じられていることCalling Zeitwerk::Loader.setup multiple times on the same loader raises a Zeitwerk::Error
測定結果Second call to loader.setup does NOT raise an error
-
gemサンプル契約ruby · linux/x64zeitwerk@2.8.3
信じられていることCalling loader.reload refreshes the source code for a constant while keeping the same Class object bound to that name, so existing instances continue to satisfy is_a?(Widget) and case/when Widget after reload.
測定結果After loader.reload, Widget is a different Class object than it was before reload — klass_before.equal?(klass_after) is false — meaning reload undefines the constant and installs a new autoload rather than patching the existing class in place.
-
gemサンプル契約ruby · linux/x64zeitwerk@2.8.3
信じられていることCalling reload and unload-like operations is enough to refresh or remove constants, so explicit pre-setup reloading configuration should not matter.
測定結果assert a loader without `enable_reloading` raises `Zeitwerk::ReloadingDisabledError` on `reload` after `setup`, and then `unload` keeps a previously loaded constant in place
-
gemサンプル契約ruby · linux/x64zeitwerk@2.8.3
信じられていることpush_dir without an explicit namespace parameter scopes autoloaded constants under a module matching the directory name.
測定結果assert push_dir with namespace left unset defaults the root namespace to Object rather than inferring a namespace from the directory name, mapping the directory to Object in all_expected_cpaths and expecting unprefixed top-level constants
-
gemサンプル契約ruby · linux/x64zeitwerk@2.8.2
信じられていることLoader callback APIs are expected to accept only bare constant names, so `::User` should be rejected as an invalid path.
測定結果assert `Zeitwerk::Loader#on_load` accepts a leading double-colon constant path and does not raise at registration (`::User`)
-
gemサンプル契約ruby · linux/x64sorbet-runtime@0.6.13427
信じられていることThe legacy `pii:` property option is still accepted as a backward-compatible alias for `sensitivity:` in sorbet-runtime v0.x.
測定結果defining a `T::Struct` prop with `pii:` raises ArgumentError and the message says `pii:` was renamed to `sensitivity:`
-
gemサンプル契約ruby · linux/x64sorbet-runtime@0.6.13427
信じられていることBecause T::Struct declares prop types and the .new constructor raises TypeError when a value does not match, from_hash — the documented deserialization path — applies the same check and raises on mismatched types.
測定結果T::Struct.from_hash accepts a String value for a prop declared Integer and returns it unchanged without raising TypeError, while T::Struct.new raises TypeError for the identical input — proving that the deserialization path skips the sig-based check the constructor applies
-
gemサンプル契約ruby · linux/x64sorbet-runtime@0.6.13427
信じられていることReplacing a `sig`-annotated method with a plain method definition should discard the prior runtime signature metadata so internal signature lookup returns no stale declaration for that method key.
測定結果After redefining a typed method without adding a new `sig`, `T::Private::Methods.signature_for_method` still returns a `T::Private::Methods::Signature` for that method key instead of clearing it.
ここの行を確かめる方法
サンプルを開き、contract を読み、実行してください。contract はそのサンプル自身のテストです。ネットワークを切った固定コンテナで実行され、その実行の署名済みレシートがネットワークに保存されます。ここに書かれていることはライブラリについての解釈ではなく、ライブラリが実際に行ったことだけに基づいています。
公開済みのサンプルのうち、このページにないものがあります。契約は通過しておりサンプルも生きていますが、その契約に文として読める行がないからです。expect(x).toBe(1) のような断言は、検査している思い込みの隣に置いても読者に何も伝えません。読めない証拠を載せるより、空けておくことを選びました。