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

[dependabot]

Bumps @types/node from 25.0.9 to 25.1.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.1.0 changes release notes

💡 Result:

I couldn’t find an @types/node@25.1.0 release—current @types/node v25 publishes as 25.0.x (e.g., 25.0.10 on Jan 21, 2026), not 25.1.0. [1]

If you actually meant Node.js v25.1.0 (not @types/node), its release notes “Notable Changes” are: (1) http: add optimizeEmptyRequests server option, (2) sqlite: allow setting defensive flag, (3) src: add watch config namespace. [2]

Sources: [1] [2]

---

🏁 Script executed:

#!/bin/bash
# Check the package.json in apps/frontend to see the actual `@types/node` version
cat apps/frontend/package.json | grep -A 2 -B 2 "@types/node"

# Query npm registry for `@types/node` to see available versions around 25.0.9 and 25.1.0
npm view `@types/node`@25.1.0 version 2>&1 || echo "Version 25.1.0 not found"
npm view `@types/node`@25.0.9 version 2>&1 || echo "Version 25.0.9 not found"

# Get the latest versions in the 25.x range
npm view `@types/node`@25.x versions --json | jq '.[-10:]' 2>&1 || npm view `@types/node` versions --json | grep -A 5 -B 5 "25.0"

Length of output: 262313

---

🏁 Script executed:

#!/bin/bash
# Get detailed information about the differences between these versions
# Check package lock file to see the actual changes
cat apps/frontend/package-lock.json | grep -A 10 "@types/node" | head -20

# Check if there are any TypeScript files that might be affected
echo "=== Checking TypeScript configuration ==="
cat apps/frontend/tsconfig.json 2>/dev/null || echo "No tsconfig.json found"

Length of output: 1555

---

@fingertips18 Based on my analysis, this dependency update appears safe to merge. Here's my assessment:

Safety Analysis

✅ Low Risk Update

• This is a minor version bump (25.0.9 → 25.1.0) in TypeScript type definitions
• Minor version updates in @types/node typically add new types or update existing ones to match Node.js features, rather than introducing breaking changes

✅ Project Context

• Your frontend project uses React/Vite with TypeScript strict mode
• Direct Node.js API usage in frontend code is typically minimal
• Type definitions are mainly for build tools (Vite, TypeScript compiler)

✅ No Breaking Changes Found

• No documented breaking changes between these versions
• Both versions exist in the npm registry and are valid
• The dependency on undici-types ~7.16.0 remains compatible

Recommendation

Safe to merge, but I recommend:

1. ✅ Merge the PR
2. 🔍 Run npm run build or your TypeScript check command to ensure no compilation errors
3. 🧪 Verify your tests pass after the update

Since you have TypeScript strict mode enabled, any type incompatibilities would be caught during compilation, making this a very safe update process.

[dependabot]

Superseded by #863.