Beispiel
Preserve custom timestamp and sequence options in UUIDv7 generation instead of silently discarding msecs to epoch zero
sha256:1ea156854e9d9790ef435039f48dd14740346e2298e632d0a2256919d714c656
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Preserve custom timestamp and sequence options in UUIDv7 generation instead of silently discarding msecs to epoch zero HOW
- Pakete
- uuid 11.1.1
- Umgebung
- node
- Erstellt
- 2026-08-16T07:08:08Z
Contract
- assert v7({ msecs }) encodes the exact 48-bit timestamp into UUID bytes 0..5
- assert v7({ msecs }) produces a valid RFC 9562 UUID with version 7 without zeroing timestamp to 1970 epoch
- assert v7({ msecs, seq }) preserves user-supplied timestamp and sequence values
- assert v7() without options maintains monotonic ordering and isolates state from explicit-options calls
Dateien
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9