chore(deps-dev): bump @types/node from 22.15.32 to 24.0.15 in /moonbit-tour

[dependabot]

Bumps @types/node from 22.15.32 to 24.0.15.

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)

[peter-jerry-ye-code-review]

Major version bump in @types/node may introduce breaking changes

Category
Correctness
Code Snippet
Lines 16 and 22-23 in package.json and pnpm-lock.yaml:

• "@types/node": "^22.10.2",

• "@types/node": "^24.0.15",
  Recommendation
  Review the CHANGELOG for @types/node v24 to identify any breaking changes that might affect the codebase. Consider testing thoroughly before merging, especially if the project uses Node.js-specific APIs. You may want to update gradually to v23 first if compatibility issues arise.
  Reasoning
  Jumping from v22 to v24 skips an entire major version, which typically indicates breaking changes in TypeScript type definitions. This could cause compilation errors or type mismatches in existing code.

Inconsistent dependency versions in lock file

Category
Maintainability
Code Snippet
Lines 2710-2713 in pnpm-lock.yaml:
'@zenfs/[email protected]':
dependencies:

•  '@types/node': 22.15.32
  

•  '@types/node': 22.16.5
  

Recommendation
Ensure all dependencies use the same version of @types/node. Consider running 'pnpm update' or 'pnpm install' to resolve version conflicts and ensure dependency consistency across the project.
Reasoning
The lock file shows @zenfs/core is still using @types/node v22.16.5 while the main project now uses v24.0.15. This version mismatch could lead to type conflicts and unpredictable behavior.

Multiple versions of undici-types being installed

Category
Performance
Code Snippet
Lines 2339-2344 and 5047-5049 in pnpm-lock.yaml:
[email protected]:
resolution: {...}
[email protected]:
resolution: {...}
Recommendation
Review if both versions of undici-types are actually needed. Consider updating all dependencies to use the same version of undici-types to reduce bundle size and avoid potential conflicts.
Reasoning
Having multiple versions of the same dependency increases bundle size and can lead to runtime issues. The newer @types/node v24 uses undici-types v7.8.0 while other dependencies still use v6.21.0.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.