build(deps-dev): bump @types/node from 22.19.15 to 25.7.0

[dependabot]

Bumps @types/node from 22.19.15 to 25.7.0.

Commits

• See full diff in compare view

[github-actions]

React Compiler Report

Commit: ce9e78428f

3 files scanned · 2 compiled · 3 skipped

File	Component	Reason
failing.tsx:6	ConditionalHook	InvalidReact Hooks must always be called in a consistent order, and may not be called conditionally.
failing.tsx:15	RefMutation	InvalidReact Cannot access refs during render
failing.tsx:16	RefMutation	InvalidReact Cannot access refs during render

Fix with AI

Fix the following React Compiler issues. The compiler skipped these components because they violate the Rules of React.

Rules:
- Do not add useMemo, useCallback, or React.memo. The compiler handles memoization once the code follows the rules.
- Do not change the underlying logic or behavior of any component.
- If a fix requires restructuring, extract helper functions rather than rewriting the component.

File: failing.tsx
  - ConditionalHook (line 6): Hooks must always be called in a consistent order, and may not be called conditionally. See the Rules of Hooks (https://react.dev/warnings/invalid-hook-call-warning)
  - RefMutation (line 15): Cannot access refs during render
    React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
  - RefMutation (line 16): Cannot access refs during render
    React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)

1 opted out ("use no memo")

• opted-out.tsx:2 useCustomHook