示例

RFC 9562 UUIDv7 encodes 48-bit Unix epoch milliseconds in the most significant bytes for chronological sorting, while v1ToV6 and v6ToV1 provide lossless bidirectional conversion between UUIDv1 and sortable UUIDv6

sha256:3ede91be1ec866fb02f7ef628bc245da3c78a87a298ebb0182a2b8391ff9cb4c

案例

目标

RFC 9562 UUIDv7 encodes 48-bit Unix epoch milliseconds in the most significant bytes for chronological sorting, while v1ToV6 and v6ToV1 provide lossless bidirectional conversion between UUIDv1 and sortable UUIDv6 HOW

包

uuid 14.0.1

环境

node

创建时间

2026-08-17T20:44:23Z

常见的想当然

UUIDv1 strings sort chronologically by generation time, or converting between UUID versions requires manually decoding and recalculating timestamp fields

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

• UUIDv7 encodes Unix epoch milliseconds in its first 48 bits, ensuring generated UUIDs sort lexicographically in chronological order across millisecond timestamps
• UUIDv7 extracts the exact 48-bit big-endian millisecond timestamp passed via options.msecs
• UUIDv7 with identical timestamps sorts strictly by sequence number
• v1ToV6 reorders UUIDv1 timestamp fields into high-mid-low order into a valid UUIDv6 that sorts chronologically
• v6ToV1 losslessly restores the original UUIDv1 from a UUIDv6 representation
• v1ToV6 and v6ToV1 accept either formatted UUID strings or 16-byte Uint8Array buffers and return the matching representation
• v7 throws Error when provided with a random byte array shorter than 16 bytes
• v1ToV6 and v6ToV1 throw TypeError on invalid UUID strings

文件

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test/contract.mjs

下载源代码构件 (tar.gz)

原始种子者

csx-seed

验证回执

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9