JSWorld Conference 2026 in Amsterdam is one of the largest JavaScript events in Europe. The 2026 edition featured a dedicated track on identifier patterns — with UUID v7 central to discussions about database primary keys, React Server Component patterns, and edge runtime generation. See UUID in JavaScript for the practical guide.
Event details
| Conference | JSWorld Conference 2026 |
| Date | February 26–28, 2026 |
| Location | Amsterdam, Netherlands |
| Focus | UUID v7 in the JavaScript ecosystem |
Key sessions
UUID v7 as the JavaScript default identifier
The opening talk argued that UUID v4 should be replaced by UUID v7 as the default ID type for new JavaScript projects. Highlights:
- The
uuidnpm package shipsv7()as a first-class export from v9.0+ - UUID v7 strings sort lexicographically in chronological order —
array.sort()gives time order - UUID v7’s 48-bit timestamp prefix eliminates
createdAtas a sort column in databases - Edge runtimes (Cloudflare Workers, Deno Deploy) support UUID v7 —
performance.timeOrigin + performance.now()provides millisecond timestamps
The uuid npm package v7 API
import { v7 as uuidv7, validate, version } from 'uuid';
// Generate UUID v7
const id = uuidv7();
// '018fbe3a-4c5d-7b12-8f3e-1a2b3c4d5e6f'
// Validate
validate(id); // true
version(id); // 7
// Custom timestamp (for testing/seeding)
const seeded = uuidv7({ msecs: new Date('2026-01-01').getTime() });
See UUID in JavaScript for the full API reference.
crypto.randomUUID() vs uuid v7
// crypto.randomUUID() — always UUID v4
const v4id = crypto.randomUUID();
// 'e4d909c2-90d5-4a5e-b5f8-3b37e9e8f2a3' (random, no timestamp)
// uuid npm package — UUID v7
import { v7 as uuidv7 } from 'uuid';
const v7id = uuidv7();
// '018fbe3a-4c5d-7b12-8f3e-1a2b3c4d5e6f' (timestamp prefix)
// Key difference: sorting
const ids = [uuidv7(), uuidv7(), uuidv7()];
ids.sort(); // Chronological order for v7; random order for v4
See crypto.randomUUID() Browser and Runtime Support.
React Server Components and UUID v7
// ✅ Correct: generate UUID v7 in Server Component
// app/orders/page.tsx (Next.js App Router)
import { v7 as uuidv7 } from 'uuid';
export default async function OrdersPage() {
// Server-side: UUID v7 generation is safe
const sessionId = uuidv7();
return <OrderList sessionId={sessionId} />;
}
// ❌ Wrong: generates UUID in client component — hydration mismatch
'use client';
import { v7 as uuidv7 } from 'uuid';
export function BadComponent() {
const id = uuidv7(); // Different on server vs client render!
return <div data-id={id}>...</div>;
}
See UUID in React and Next.js.
Edge runtime UUID v7 generation
// Cloudflare Workers
export default {
async fetch(request: Request): Promise<Response> {
const { v7: uuidv7 } = await import('uuid');
const traceId = uuidv7();
return new Response(JSON.stringify({ traceId }), {
headers: {
'Content-Type': 'application/json',
'X-Trace-ID': traceId,
},
});
},
};
// Deno Deploy
import { v7 as uuidv7 } from 'npm:uuid';
Deno.serve((req) => {
const traceId = uuidv7();
return Response.json({ traceId }, {
headers: { 'X-Trace-ID': traceId },
});
});
Sorting and pagination with UUID v7
// UUID v7 arrays sort chronologically with standard sort()
const ids = Array.from({ length: 5 }, () => uuidv7());
ids.sort(); // Already in creation order
// Cursor pagination with UUID v7
async function fetchPage(cursor?: string) {
const params = cursor ? `?cursor=${cursor}` : '';
const res = await fetch(`/api/orders${params}`);
return res.json();
}
See UUID v7 for Cursor Pagination.
Conference takeaways
- Replace
crypto.randomUUID()withuuidv7()for new projects — same API surface, time-ordered output - Server-only UUID v7 in React — never generate in client components to avoid hydration mismatches
- Edge runtimes support UUID v7 — all major runtimes have
Date.now()and CSPRNG, which are all UUID v7 needs - UUID v7 strings sort correctly with
Array.sort()— lexicographic = chronological - Drop
createdAtfrom APIs — UUID v7 ID encodes creation time, clients can extract it
Further reading
- UUID in JavaScript — Full Guide
- crypto.randomUUID() Browser and Runtime Support
- UUID in React and Next.js — Patterns and Pitfalls
- UUID in Edge Functions
- UUID v7 for Cursor Pagination
External references
Frequently asked questions
What UUID v7 topics were discussed at JSWorld 2026?
JSWorld 2026 sessions covered UUID v7 in the full JavaScript stack: the uuid npm package's v7() function, why crypto.randomUUID() only generates UUID v4, React and Next.js hydration patterns for server-generated UUIDs, Node.js and Bun runtime UUID performance, and edge function UUID generation on Cloudflare Workers and Vercel Edge. See UUID in JavaScript.
Why does crypto.randomUUID() not generate UUID v7?
crypto.randomUUID() is defined by the Web Crypto API specification to generate UUID v4 — 122 bits of random data with no timestamp. The spec predates RFC 9562. For UUID v7 in browsers, use the uuid npm package or the uuidv7 package. See crypto.randomUUID() Browser and Runtime Support.
How does UUID v7 interact with React Server Components?
Generate UUID v7 only in Server Components or server actions — never in client components. Client-side UUID generation causes hydration mismatches because the server-rendered HTML has the server-generated UUID but React rehydration runs UUID generation again on the client, producing a different value. Pass the UUID from server to client as a prop. See UUID in React and Next.js.