refactor: remove uuid dependency

[AnastasiyaHladina]

This PR drops the uuid package from node modules and replaces it with standard randomUUID usage.

Node.js crypto
Web crypto

Summary by CodeRabbit

• Refactor
  • Replaced third-party ID generation with built-in secure ID generation across runs, browsers, webhooks, workflows, and storage. No functional or UI changes.
• Chores
  • Removed legacy UUID libraries from the project to reduce dependency surface and simplify maintenance.

[coderabbitai]

Walkthrough

Replaces usages of the external uuid library with built-in crypto.randomUUID across server and client code and removes uuid-related dependencies from package.json. No API signatures, control flow, or behavior were changed.

Changes

Cohort / File(s)	Summary
Dependency cleanup package.json	Removed uuid, uuidv4, and @types/uuid dependencies.
Server UUID migration server/src/api/record.ts, server/src/browser-management/controller.ts, server/src/routes/storage.ts, server/src/routes/webhook.ts, server/src/schedule-worker.ts, server/src/workflow-management/classes/Generator.ts, server/src/workflow-management/scheduler/index.ts	Replaced uuid()/v4() usage with crypto.randomUUID() and updated imports to Node’s crypto. ID generation sites updated; no logic or control-flow changes.
Client UUID migration src/components/integration/IntegrationSettings.tsx, src/components/robot/pages/RobotIntegrationPage.tsx	Replaced client-side uuid() usage with crypto.randomUUID() and removed unused uuid imports. No UI or behavioral changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: webhook support  #610 — Related webhook feature changes; touches webhook routes and UI modified here.
• Revert "fix: prevent page reload on run trigger to open remote browser" #388 — Changes to remote browser creation flow in server/src/browser-management/controller.ts, overlapping this PR's edits.
• feat: modal to UI pages #719 — Modifications to RobotIntegrationPage and related components that overlap client-side webhook code here.

Suggested labels

Type: Chore

Suggested reviewers

• RohitR311
• amhsirak

Poem

Hoppity-hop, I swap IDs with a grin,
No extra packages—just randomness within.
Runs, hooks, and browsers now sparkle anew,
A tiny rabbit's patch—clean, quick, and true. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly summarizes the primary change of the pull request by indicating the removal of the uuid dependency through a refactor without extra noise, making it concise and fully aligned with the diff's main focus.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 794291c and c899026.

📒 Files selected for processing (2)

• server/src/routes/storage.ts (4 hunks)
• server/src/schedule-worker.ts (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• server/src/routes/storage.ts

🔇 Additional comments (2)

server/src/schedule-worker.ts (2)

5-5: LGTM! Clean migration to built-in crypto module.

The import correctly uses Node.js's built-in crypto.randomUUID(), eliminating the need for an external uuid package.

---

36-36: Approve UUID refactor and enforce Node >= 14.17.0.

Replacing uuid() with crypto.randomUUID() is correct and preserves RFC 4122 v4 behavior. Ensure your runtime supports randomUUID() by adding a Node.js version requirement (e.g. an engines.node entry in package.json or a .nvmrc set to >=14.17.0).

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

server/src/schedule-worker.ts (1)

36-36: Consider using the imported function for consistency.

Line 36 uses crypto.randomUUID() while line 9 imports randomUUID. For consistency with other files in this PR (e.g., record.ts, scheduler/index.ts), consider using the imported function directly.

Apply this diff:

-    const runId = crypto.randomUUID();
+    const runId = randomUUID();

server/src/routes/storage.ts (1)

610-610: Consider documenting the placeholder browserId for queued runs.

The placeholder browserId is assigned here even though no browser exists yet. This ID is later replaced with a real browser ID when the run is processed (line 1029 in processQueuedRuns). While functionally correct, this might be clearer with an inline comment or by using a distinct naming pattern (e.g., prefix with "queued-").

Example with comment:

-      const browserId = randomUUID();
+      // Temporary placeholder ID - will be replaced with actual browser ID when run is processed
+      const browserId = randomUUID();

Alternatively, consider using a more descriptive temporary ID:

-      const browserId = randomUUID();
+      const browserId = `queued-${randomUUID()}`;

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 833fe59 and 794291c.

📒 Files selected for processing (10)

• package.json (0 hunks)
• server/src/api/record.ts (2 hunks)
• server/src/browser-management/controller.ts (3 hunks)
• server/src/routes/storage.ts (4 hunks)
• server/src/routes/webhook.ts (2 hunks)
• server/src/schedule-worker.ts (2 hunks)
• server/src/workflow-management/classes/Generator.ts (2 hunks)
• server/src/workflow-management/scheduler/index.ts (3 hunks)
• src/components/integration/IntegrationSettings.tsx (1 hunks)
• src/components/robot/pages/RobotIntegrationPage.tsx (1 hunks)

💤 Files with no reviewable changes (1)

• package.json

🧰 Additional context used

🧬 Code graph analysis (1)

server/src/routes/webhook.ts (1)

server/src/routes/index.ts (1)

• webhook (16-16)

🔇 Additional comments (10)

src/components/integration/IntegrationSettings.tsx (1)

199-199: LGTM! Verify secure context in deployment.

The migration from uuid() to crypto.randomUUID() is correct. Note that the Web Crypto API's randomUUID() requires a secure context (HTTPS or localhost), so ensure the application is served over HTTPS in production.

server/src/api/record.ts (1)

10-10: LGTM!

The migration to Node.js built-in crypto.randomUUID() is correct and eliminates the external uuid dependency. The generated IDs maintain RFC 4122 v4 UUID format compatibility.

Also applies to: 492-492

server/src/routes/webhook.ts (1)

5-5: LGTM!

The webhook ID generation correctly uses the built-in crypto.randomUUID() with proper fallback logic when webhook.id is not provided.

Also applies to: 89-89

src/components/robot/pages/RobotIntegrationPage.tsx (1)

204-204: LGTM! Same secure context requirement as IntegrationSettings.tsx.

The migration to crypto.randomUUID() is correct. As with IntegrationSettings.tsx (line 199), ensure the application runs in a secure context (HTTPS or localhost) since the Web Crypto API requires it.

server/src/workflow-management/scheduler/index.ts (1)

1-1: LGTM!

Both runId and runByScheduleId correctly use the built-in crypto.randomUUID(), maintaining UUID format compatibility while eliminating the external dependency.

Also applies to: 50-50, 63-63

server/src/workflow-management/classes/Generator.ts (1)

18-18: LGTM!

The recording metadata ID generation correctly uses crypto.randomUUID(), ensuring new robots receive valid UUID v4 identifiers without the external uuid dependency.

Also applies to: 907-907

server/src/browser-management/controller.ts (1)

6-6: LGTM!

Browser ID generation correctly uses crypto.randomUUID() in both the fallback case (line 24) and direct assignment (line 70), maintaining consistent UUID format while removing the external dependency.

Also applies to: 24-24, 70-70

server/src/routes/storage.ts (3)

7-7: LGTM! Clean migration to native crypto API.

The switch from the uuid package to Node.js's built-in crypto.randomUUID() is correct. Both generate RFC 4122 version 4 UUIDs, so the format remains identical.

---

397-401: LGTM! Correct ID generation for robot duplication.

Both the robot ID and recording metadata ID are properly generated using randomUUID(), ensuring unique identifiers for the duplicated robot.

---

521-521: LGTM! Proper runId generation.

The runId is correctly generated upfront using randomUUID() before the browser availability check, allowing it to be used consistently in both execution paths.