CodeSampleX

Was das Netzwerk gefunden hat

Jede Zeile hier ist eine Messung, keine Meinung. Jede verweist auf ein veröffentlichtes Sample, dessen Contract in einem gepinnten Container ohne Netzzugang ausgeführt wird — Sie können ihn erneut ausführen und dem Ergebnis widersprechen.

Betriebssystem und Runtime stammen aus der aufgezeichneten Sample-Umgebung; fehlende Dimensionen werden ausgeschlossen.

597 Befunde aus 8 Ökosystemen.

Vom Sample behauptet, vom Vertrag gemessen

351–375 von 568, gemessen von veröffentlichten Samples.

  1. npmSample-Vertragnode · linux/x64marked@17.0.3

    AngenommenMarkdown image alt text containing double quotes is rendered with HTML entity escaping so the attribute value does not break out of quotes.

    Gemessenmarked.parse escapes double quotes inside image alt text as " rather than emitting raw unescaped double quotes inside alt attributes

  2. npmSample-Vertragnode · linux/x64luxon@3.7.2

    AngenommenConfiguring Settings.defaultZone causes DateTime zone specifiers and setZone calls specifying 'system' to resolve to that configured default zone.

    GemessenWhen 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.

  3. npmSample-Vertragnode · linux/x64luxon@3.5.0

    AngenommenSetting Settings.defaultZone overrides the zone for DateTime instances created or converted with the system zone specifier.

    GemessenDateTime setZone('system') returns a SystemZone instance with type system rather than inheriting Settings.defaultZone.

  4. npmSample-Vertragnode · linux/x64luxon@3.6.1

    AngenommenLooking up an invalid IANA timezone string such as 'constructor' in Luxon returns an invalid IANAZone object rather than the native Object constructor function.

    GemessenIANAZone.create('constructor') returns an invalid IANAZone instance with isValid equal to false rather than returning the native Object constructor function.

  5. npmSample-Vertragnode · linux/x64luxon@3.5.0

    AngenommenWhen throwOnInvalid is enabled, Luxon throws public custom error classes whose name property matches their constructor name.

    GemessenLuxon'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.

  6. npmSample-Vertragnode · linux/x64luxon@3.7.2

    AngenommenDateTime.fromObject parses timezone configuration specified directly inside the date/time units object.

    GemessenDateTime.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.

  7. npmSample-Vertragnode · linux/x64jest@30.4.2

    Angenommenexpect(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.

    Gemessenexpect(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.

  8. npmSample-Vertragnode · linux/x64jest@30.4.2

    AngenommenPassing an empty array to test.each() safely runs zero tests, mirroring how JavaScript iteration handles empty arrays.

    GemessenCalling test.each([]) throws a fatal error that crashes the test suite, rather than gracefully skipping and running zero tests.

  9. npmSample-Vertragnode · linux/x64jest@30.4.2

    AngenommenA 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.

    Gemessenjest.resetModules() alone fails to restore the original implementation of a mocked dependency because Jest retains the mock definition in its registry.

  10. npmSample-Vertragnode · linux/x64jest@29.7.0

    AngenommenbeforeEach and afterEach hooks run for every test block defined in the file, including concurrent tests.

    Gemessentest.concurrent bypasses beforeEach and afterEach hooks, executing concurrent tests without running the setup and teardown hooks.

  11. npmSample-Vertragnode · linux/x64jest@29.7.0

    AngenommenJest's expect(a).toEqual(b) and expect(a).toStrictEqual(b) perform deep property equality on Error instances and fail when custom error properties differ.

    Gemessenexpect(errA).toEqual(errB) passes when errA and errB are Error instances with identical messages but different custom properties like code or statusCode.

  12. npmSample-Vertragnode · linux/x64jest@30.4.2

    Angenommenjest.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.

    GemessenCalling 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.

  13. npmSample-Vertragnode · linux/x64jest@29.7.0

    AngenommenJest automatically clears mock function call history between tests by default.

    GemessenMock 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.

  14. npmSample-Vertragnode · linux/x64jest@29.7.0

    AngenommenCalling 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.

    Gemessenjest.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').

  15. npmSample-Vertragnode · linux/x64jest@29.7.0

    AngenommenA test setup file configured under setupFiles has access to test framework globals like beforeEach, afterEach, and expect.extend.

    Gemessenassert running Jest with test framework hooks in setupFiles fails with ReferenceError: beforeEach is not defined because the framework environment is not yet initialized

  16. npmSample-Vertragnode · linux/x64jest@30.4.2

    AngenommenCalling jest.resetAllMocks() restores functions spied on with jest.spyOn() back to their original unmocked implementation.

    Gemessenjest.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.

  17. npmSample-Vertragnode · linux/x64jest@30.4.2

    AngenommenA named ESM import from such a CommonJS module should always resolve to the corresponding own-property function export.

    GemessenJest 30.4.2 keeps named imports working for a CommonJS module where `module.exports` is a function with own-property exports.

  18. npmSample-Vertragnode · linux/x64happy-dom@20.11.2

    AngenommenHappy DOM writes console output directly to the host console, and filtering virtual console output leaves unmatched entries queued for a later read.

    GemessenA default Window buffers log, warn, and error calls as exact structured entries with type, level, message, and null group metadata

  19. npmSample-Vertragnode · linux/x64happy-dom@20.11.2

    AngenommenThe CSS attribute selector [attr~="val"] treats hyphens as word boundaries and matches substrings in hyphenated attribute values.

    Gemessenchild.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

  20. npmSample-Vertragnode · linux/x64express@4.18.2

    AngenommenAll registered synchronous handlers on a single route will execute in sequence regardless of the stack size exceeding 100 handlers.

    GemessenExpress 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.

  21. npmSample-Vertragnode · linux/x64express@5.2.1

    Angenommenreq.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.

    Gemessenreq.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

  22. npmSample-Vertragnode · linux/x64express@4.22.2

    AngenommenExpress executes middlewares and route handlers in strict sequential order, preventing subsequent routes from running until preceding async middlewares complete and call next().

    GemessenA downstream route handler is executed before a preceding async middleware completes if an earlier middleware calls next() twice.

  23. npmSample-Vertragnode · linux/x64es-toolkit@1.50.0

    AngenommenPassing { leading: true, trailing: false } to debounce executes immediately on the first call and prevents delayed execution on the trailing edge.

    GemessenPassing { 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.

  24. npmSample-Vertragnode · linux/x64express@4.21.2

    AngenommenExpress 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).

    GemessenExpress 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

  25. npmSample-Vertragnode · linux/x64core-js@3.50.0

    AngenommenA core-js-provided URL.prototype.toJSON dynamically calls the current URL.prototype.toString, so reassigning toString later also changes toJSON output.

    GemessenWhen the host URL.prototype.toJSON is absent, importing core-js/actual/url installs the method while retaining a compliant native URL constructor.

Wie Sie jede Zeile hier prüfen

Öffnen Sie das Sample, lesen Sie seinen Contract, führen Sie ihn aus. Der Contract ist der eigene Test des Samples: Er läuft ohne Netz in einem gepinnten Container, und die signierte Quittung dieses Laufs ist das, was das Netzwerk speichert. Nichts hier hängt davon ab, wie wir eine Bibliothek lesen — nur davon, was sie getan hat.

Einige veröffentlichte Beispiele stehen nicht auf dieser Seite. Ihr Vertrag ist bestanden und das Beispiel ist live — aber keine Zeile dieses Vertrags liest sich als Satz. Eine Zusicherung wie expect(x).toBe(1) sagt neben der Annahme, die sie prüft, niemandem etwas. Sie bleiben lieber draußen, als als Beleg zu erscheinen, den niemand lesen kann.