ネットワークが見つけたもの
以下の各行は意見ではなく測定です。いずれも公開サンプルにリンクしており、その contract はネットワークを切った固定コンテナで実行されるので、自分で再実行して結果に反論できます。
OS とランタイムはリンク先サンプルに記録された環境です。その項目がない記録は選択時に除外されます。
597 件の発見、8 個のエコシステム。
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
サンプルが述べ、その契約が測ったこと
公開サンプルが測定した結果の 351–375 件目(全 568 件)。
-
npmサンプル契約node · linux/x64marked@17.0.3
信じられていることMarkdown image alt text containing double quotes is rendered with HTML entity escaping so the attribute value does not break out of quotes.
測定結果marked.parse escapes double quotes inside image alt text as " rather than emitting raw unescaped double quotes inside alt attributes
-
npmサンプル契約node · linux/x64luxon@3.7.2
信じられていることConfiguring Settings.defaultZone causes DateTime zone specifiers and setZone calls specifying 'system' to resolve to that configured default zone.
測定結果When Settings.defaultZone is overridden, Info.normalizeZone('system') and DateTime.fromISO(str, { zone: 'system' }) resolve to the host environment's SystemZone rather than Settings.defaultZone, while 'default' resolves to Settings.defaultZone instead of creating an invalid DateTime.
-
npmサンプル契約node · linux/x64luxon@3.5.0
信じられていることSetting Settings.defaultZone overrides the zone for DateTime instances created or converted with the system zone specifier.
測定結果DateTime setZone('system') returns a SystemZone instance with type system rather than inheriting Settings.defaultZone.
-
npmサンプル契約node · linux/x64luxon@3.6.1
信じられていることLooking up an invalid IANA timezone string such as 'constructor' in Luxon returns an invalid IANAZone object rather than the native Object constructor function.
測定結果IANAZone.create('constructor') returns an invalid IANAZone instance with isValid equal to false rather than returning the native Object constructor function.
-
npmサンプル契約node · linux/x64luxon@3.5.0
信じられていることWhen throwOnInvalid is enabled, Luxon throws public custom error classes whose name property matches their constructor name.
測定結果Luxon's custom error classes (InvalidDateTimeError, InvalidDurationError, and InvalidIntervalError) are not exported, and their thrown instances have their name property set to 'Error' rather than their constructor names.
-
npmサンプル契約node · linux/x64luxon@3.7.2
信じられていることDateTime.fromObject parses timezone configuration specified directly inside the date/time units object.
測定結果DateTime.fromObject throws an Error containing 'Invalid unit zone' if the 'zone' property is passed in the first argument object instead of the second options argument.
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることexpect(received).toEqual(expected) and expect(received).toStrictEqual(expected) inspect all own properties on an object, failing when non-enumerable properties or non-enumerable symbols contain conflicting values.
測定結果expect(received).toEqual(expected) and expect(received).toStrictEqual(expected) pass when two objects differ only in non-enumerable properties or non-enumerable symbols because Jest 30 excludes non-enumerable properties from object matchers by default.
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることPassing an empty array to test.each() safely runs zero tests, mirroring how JavaScript iteration handles empty arrays.
測定結果Calling test.each([]) throws a fatal error that crashes the test suite, rather than gracefully skipping and running zero tests.
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることA developer might expect that resetting Jest's module cache with jest.resetModules() is sufficient to restore the original implementation of a mocked dependency when the parent module is re-required.
測定結果jest.resetModules() alone fails to restore the original implementation of a mocked dependency because Jest retains the mock definition in its registry.
-
npmサンプル契約node · linux/x64jest@29.7.0
信じられていることbeforeEach and afterEach hooks run for every test block defined in the file, including concurrent tests.
測定結果test.concurrent bypasses beforeEach and afterEach hooks, executing concurrent tests without running the setup and teardown hooks.
-
npmサンプル契約node · linux/x64jest@29.7.0
信じられていることJest's expect(a).toEqual(b) and expect(a).toStrictEqual(b) perform deep property equality on Error instances and fail when custom error properties differ.
測定結果expect(errA).toEqual(errB) passes when errA and errB are Error instances with identical messages but different custom properties like code or statusCode.
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることjest.isolateModules isolates module mocking performed with jest.doMock within its callback scope, so subsequent module require calls outside the callback return the unmocked original module.
測定結果Calling jest.doMock inside a jest.isolateModules callback mutates Jest's global mock registry, causing subsequent require calls outside the callback to receive the mock instead of the original module.
-
npmサンプル契約node · linux/x64jest@29.7.0
信じられていることJest automatically clears mock function call history between tests by default.
測定結果Mock function call history is not cleared between tests by default, so a mock function called in a previous test retains its calls in subsequent tests unless clearMocks is explicitly enabled.
-
npmサンプル契約node · linux/x64jest@29.7.0
信じられていることCalling jest.spyOn on a getter property without an accessType argument raises a TypeError for non-function properties, or following its error message to use jest.replaceProperty successfully mocks the property value.
測定結果jest.spyOn on a getter property without accessType throws a base Error rather than a TypeError and suggests using jest.replaceProperty, which then throws another base Error stating it cannot replace getter properties and recommending jest.spyOn(object, property, 'get').
-
npmサンプル契約node · linux/x64jest@29.7.0
信じられていることA test setup file configured under setupFiles has access to test framework globals like beforeEach, afterEach, and expect.extend.
測定結果assert running Jest with test framework hooks in setupFiles fails with ReferenceError: beforeEach is not defined because the framework environment is not yet initialized
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることCalling jest.resetAllMocks() restores functions spied on with jest.spyOn() back to their original unmocked implementation.
測定結果jest.resetAllMocks() clears mock call history and resets the mock implementation to return undefined rather than restoring the original unmocked method, which only jest.restoreAllMocks() or spy.mockRestore() performs.
-
npmサンプル契約node · linux/x64jest@30.4.2
信じられていることA named ESM import from such a CommonJS module should always resolve to the corresponding own-property function export.
測定結果Jest 30.4.2 keeps named imports working for a CommonJS module where `module.exports` is a function with own-property exports.
-
npmサンプル契約node · linux/x64happy-dom@20.11.2
信じられていることHappy DOM writes console output directly to the host console, and filtering virtual console output leaves unmatched entries queued for a later read.
測定結果A default Window buffers log, warn, and error calls as exact structured entries with type, level, message, and null group metadata
-
npmサンプル契約node · linux/x64happy-dom@20.11.2
信じられていることThe CSS attribute selector [attr~="val"] treats hyphens as word boundaries and matches substrings in hyphenated attribute values.
測定結果child.matches('[data-controller~="modal"]') returns false against data-controller="modal-auto-close" rather than true, because [attr~="val"] matches only whitespace-separated tokens per CSS Selectors Level 4
-
npmサンプル契約node · linux/x64express@4.18.2
信じられていることAll registered synchronous handlers on a single route will execute in sequence regardless of the stack size exceeding 100 handlers.
測定結果Express 4.18.2 executes all 105 synchronous handlers registered on a single route, whereas Express 4.18.1 skips the 101st handler due to an off-by-one error during sync stack threshold reset.
-
npmサンプル契約node · linux/x64express@5.2.1
信じられていることreq.is('json') evaluates the Content-Type header directly regardless of whether a body was sent, req.range() returns empty arrays or null on invalid or unsatisfiable byte ranges, and req.accepts() returns true for any media type mentioned in the Accept header.
測定結果req.is('json') returns null when the request lacks body headers such as Content-Length or Transfer-Encoding even if Content-Type application/json is present, returning the matched type string only when a body is actually transmitted
-
npmサンプル契約node · linux/x64express@4.22.2
信じられていることExpress executes middlewares and route handlers in strict sequential order, preventing subsequent routes from running until preceding async middlewares complete and call next().
測定結果A downstream route handler is executed before a preceding async middleware completes if an earlier middleware calls next() twice.
-
npmサンプル契約node · linux/x64es-toolkit@1.50.0
信じられていることPassing { leading: true, trailing: false } to debounce executes immediately on the first call and prevents delayed execution on the trailing edge.
測定結果Passing { leading: true, trailing: false } to es-toolkit debounce fails to invoke immediately because edges defaults to ['trailing'] unless configured as { edges: ['leading'] }, while trailing execution still fires on timeout.
-
npmサンプル契約node · linux/x64express@4.21.2
信じられていることExpress identifies error-handling middleware by checking if the first argument is an error or omitting the unused next parameter like (err, req, res) still catches errors passed to next(err).
測定結果Express skips 3-parameter error handlers (err, req, res) during error routing because it identifies error middleware solely by checking fn.length === 4, executing only 4-parameter functions (err, req, res, next) while running 3-parameter functions on normal requests with shifted arguments
-
npmサンプル契約node · linux/x64core-js@3.50.0
信じられていることA core-js-provided URL.prototype.toJSON dynamically calls the current URL.prototype.toString, so reassigning toString later also changes toJSON output.
測定結果When the host URL.prototype.toJSON is absent, importing core-js/actual/url installs the method while retaining a compliant native URL constructor.
ここの行を確かめる方法
サンプルを開き、contract を読み、実行してください。contract はそのサンプル自身のテストです。ネットワークを切った固定コンテナで実行され、その実行の署名済みレシートがネットワークに保存されます。ここに書かれていることはライブラリについての解釈ではなく、ライブラリが実際に行ったことだけに基づいています。
公開済みのサンプルのうち、このページにないものがあります。契約は通過しておりサンプルも生きていますが、その契約に文として読める行がないからです。expect(x).toBe(1) のような断言は、検査している思い込みの隣に置いても読者に何も伝えません。読めない証拠を載せるより、空けておくことを選びました。