Add fallback ID generator for environments without crypto.randomUUID

[shiye515]

Summary

Replace direct crypto.randomUUID() usage in browser-executed code with a shared ID helper that falls back when globalThis.crypto?.randomUUID is unavailable.

Changes

• add src/lib/create-id.ts
• replace direct UUID generation in useEditorTabs.ts
• replace direct UUID generation in staged-changes.ts

Why

Some users running the app via Docker hit a browser-side runtime error:

index-03aNhJ-r.js:1468 Uncaught (in promise) TypeError: crypto.randomUUID is not a function
    at index-03aNhJ-r.js:1468:15414
    at Array.map (<anonymous>)
    at index-03aNhJ-r.js:1468:15214
    at handleExecute (index-03aNhJ-r.js:1460:723)

This change avoids relying on crypto.randomUUID() being present in all client environments.

[vercel]

@shiye515 is attempting to deploy a commit to the bytebase Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

This PR adds a shared browser-safe ID helper for code paths that previously called crypto.randomUUID() directly. The main changes are:

• Added src/lib/create-id.ts with a randomUUID path and fallback path.
• Switched SQL result tab ID creation to use the helper.
• Switched staged delete, insert, and update change IDs to use the helper.

Confidence Score: 4/5

This is close, but the fallback should be hardened before merging.

• The direct crypto.randomUUID() crash path is addressed.

• The fallback can still produce duplicate IDs in the same millisecond.

• Duplicate IDs can confuse result tab state and staged change removal.

• src/lib/create-id.ts should make fallback IDs unique within the running app.

Important Files Changed

Filename	Overview
src/lib/create-id.ts	Introduces the shared ID helper and fallback path used by the changed callers.
src/components/sql-editor/hooks/useEditorTabs.ts	Uses the new helper for result tab IDs, which are later used as UI and state keys.
src/lib/staged-changes.ts	Uses the new helper for staged change IDs used by staged-change operations.

_{Reviews (1): Last reviewed commit: "Add fallback ID generator for environmen..." | Re-trigger Greptile}

[greptile-apps]

Fallback IDs can collide The fallback ID only combines the current millisecond with Math.random(). When two IDs are created in the same millisecond and Math.random() repeats or has weak entropy, callers receive duplicate IDs. Result tabs use these IDs as React keys and as keys into displayRowsMap, so duplicate IDs can make two result tabs share row state or make tab selection point at the wrong result. Staged changes also remove entries by matching ID, so a duplicate can remove more than one change.

Suggested change

	return `id-${Date.now()}-${Math.random().toString(36).slice(2, 11)}`
	const random = Math.random().toString(36).slice(2, 11)
	return `id-${Date.now()}-${random}-${createId.counter++}`

[shiye515]

The program runs on the client side, and the scenario described above is very unlikely to happen. If you really want to avoid this situation completely, you can use the third-party library uuid.

[shiye515]

When a web page is opened using a non‑HTTPS link, the crypto.randomUUID() function is unavailable.