Update dependency @types/node to v24

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	^20.10.1 → ^24.0.0
@types/node (source)	^22.13.10 → ^24.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6cdd179

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[devin-ai-integration]

Devin Review found 2 new potential issues.

View 1 additional finding in Devin Review.

[devin-ai-integration]

🚩 Major version jump in @types/node may introduce breaking type changes

The livekit-server-sdk package jumps from @types/node@^20 to @types/node@^24, skipping two major versions (21, 22, 23). While this is only a devDependency and won't affect runtime behavior, @types/node major versions can introduce breaking changes to type definitions (e.g., removed or restructured types for Node.js APIs like Buffer, stream, crypto, etc.). The livekit-rtc package has a smaller jump from ^22 to ^24. Any type incompatibilities would surface during tsc compilation in CI, but it's worth confirming CI passes cleanly before merging.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🚩 @types/node v24 may expose APIs unavailable in supported Node versions

Both packages declare "node": ">= 18" in their engines field (packages/livekit-rtc/package.json:74, packages/livekit-server-sdk/package.json:65), meaning they claim to support Node 18, 20, 22, etc. However, @types/node@^24 provides type definitions for the Node.js 24 API surface. This means TypeScript will happily allow usage of APIs introduced in Node 20, 22, or 24 (e.g., changes to fs, crypto, stream, or global type changes) without any compiler error — even though those APIs would fail at runtime on Node 18.

This isn't a bug in itself (it's a dev dependency, so it doesn't affect consumers' type resolution), but it does reduce the safety net for contributors: new code could accidentally rely on newer Node APIs that don't exist in Node 18, and TypeScript won't catch it. Typically, @types/node major version should align with the minimum supported Node version to prevent this class of issue.

---

Was this helpful? React with 👍 or 👎 to provide feedback.