chore(deps-dev): bump @types/node from 25.0.9 to 25.2.0 in /apps/frontend

[dependabot]

Bumps @types/node from 25.0.9 to 25.2.0.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[fingertips18]

@coderabbitai Are there any breaking changes in this dependency update? Is it safe to merge?

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

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

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🌐 Web query:

`@types/node` 25.2.0 changelog breaking changes

💡 Result:

• There is no published @types/node@25.2.0 release on npm. Recent @types/node releases are 25.0.x (e.g. 25.0.10 on Jan 21, 2026), not 25.2.0. [1]
• @types/node does not have an official per-version changelog / breaking-changes log. The DefinitelyTyped maintainers have confirmed there isn’t a dedicated changelog you can follow. [2]

How to identify “breaking changes” anyway

• Treat @types/node changes as commit/PR-based, not changelog-based: find the corresponding changes under DefinitelyTyped/DefinitelyTyped/types/node, then diff the definitions between the two versions you’re upgrading. [2]

If you actually meant Node.js runtime v25.2.0 (not @types/node), its release notes are here. [3]

Sources: [1] [2] [3]

---

🏁 Script executed:

#!/bin/bash
# Check the package.json to see the actual version being updated
cat apps/frontend/package.json | grep -A2 -B2 "@types/node"

Length of output: 154

---

🌐 Web query:

`@types/node` latest version npm 2026

💡 Result:

As of Feb 2, 2026, the most recent published version of @types/node is 25.2.0 (released Feb 1, 2026). [1]

To install the npm latest dist-tag version:

• npm i -D @types/node@latest (the latest tag is what npm uses by default). [2]

Sources: [1] [2]

---

🏁 Script executed:

#!/bin/bash
# Check if there are any TypeScript compilation issues mentioned in the PR
# Look for package-lock.json to see the exact versions
if [ -f "apps/frontend/package-lock.json" ]; then
    grep -A5 '"@types/node"' apps/frontend/package-lock.json | head -20
fi

Length of output: 576

---

🌐 Web query:

`@types/node` 25.1.0 25.2.0 changes DefinitelyTyped

💡 Result:

Between @types/node@25.1.0 and @types/node@25.2.0, the typings are expected to track the Node.js 25.2.0 surface area (i.e., new/changed APIs added in Node v25.2.0, released 2025-11-11) vs Node v25.1.0 (2025-10-28). The headline deltas in Node that drive the typings update are:

• util.deprecate: adds new options (so typings should add/extend the util.deprecate signature/options type). [1]
• Node-API (N-API): adds napi_create_object_with_properties (so typings should add this N-API declaration). [1]
• V8 HeapStatistics: adds total_allocated_bytes to heap statistics (so typings for the relevant V8/heap stats shape should gain this field). [1]
• Module “type stripping” is marked stable in Node 25.2 (may affect docs/flags more than TS types, but it’s a notable runtime change between these minors). [1]
• Web Storage (localStorage) behavior change: Node 25.2.0 notes a change where access can throw in some cases (a runtime behavioral change; not necessarily a type change). [1]

For context, Node 25.1.0’s notable additions (what @types/node@25.1.x is aligned to) were:

• HTTP: optimizeEmptyRequests server option. [2]
• SQLite: ability to set a defensive flag. [2]
• --watch config: new “watch config namespace”. [2]

Sources: Node.js 25.2.0 release notes (2025-11-11) [1], Node.js 25.1.0 release notes (2025-10-28) [2].

[1] (nodejs.org)
[2] (nodejs.org)

Citations:

• 1: https://nodejs.org/en/blog/release/v25.2.0?utm_source=openai
• 2: https://nodejs.org/en/blog/release/v25.1.0?utm_source=openai

---

@fingertips18, I've checked the changes in this dependency update and here's what I found:

No Breaking Changes Detected ✅

The update from @types/node 25.0.9 to 25.2.0 (released Feb 1, 2026) contains only additive changes that align with Node.js 25.1.0 and 25.2.0 runtime updates:

New Additions:

• Extended type definitions for util.deprecate with new options
• New N-API function: napi_create_object_with_properties
• New field in V8 HeapStatistics: total_allocated_bytes
• HTTP server option: optimizeEmptyRequests
• SQLite defensive flag support
• Type stripping module support (now stable)

All these changes add new types and properties without removing or modifying existing APIs, making this update backward-compatible.

Safety Assessment

✅ Safe to merge - This is a routine type definitions update with no breaking changes.

Recommendations:

1. Ensure your CI/build checks pass to confirm no unexpected TypeScript compilation issues
2. The caret range (^25.2.0) will automatically accept future patch updates

The Dependabot compatibility score and automated checks should also give you confidence in this update.