Skip to content

chore: resolve complex Dependabot dependency upgrades requiring code changes #255

@hessius

Description

@hessius

Overview

Three Dependabot PRs targeting main cannot be merged by simply updating the lockfile — they require coordinated code or configuration changes. This issue tracks the implementation work needed.


PR #243lucide-react 0.484.0 → 0.576.0

Why it needs work:
resizable.tsx imports via a private internal path:
```ts
import GripVerticalIcon from "lucide-react/dist/esm/icons/grip-vertical"
```
This bypasses the public API and is not guaranteed to be stable across releases. With 92 minor-version steps, the internal dist structure may have changed.

Required:


PR #246@eslint/js 9.39.3 → 10.0.1

Why it needs work:
`@eslint/js@10` declares `eslint@^10.0.0` as a required peer dependency, but the project currently uses `eslint@9.28.0`. Installing both would produce a peer-dependency conflict.

This upgrade requires a coordinated ESLint v10 upgrade:


PR #249eslint-plugin-react-hooks 5.2.0 → 7.0.1

Why it needs work:
Jumping two major versions (5 → 7) introduces new/changed lint rules. The project uses `...reactHooks.configs.recommended.rules` in `eslint.config.js`, which automatically adopts all recommended rules. New stricter rules in v6/v7 (e.g., changes to `exhaustive-deps`, new rules around hook usage) could cause CI failures on existing code.

Additionally, `eslint-plugin-react-hooks@7` peer-dependency range only covers `eslint@^9` — it does not explicitly list `eslint@^10`. This makes it part of the same coordinated ESLint upgrade work as PR #246.

Required:


Recommended order of implementation

  1. Fix lucide-react import in resizable.tsx (independent, low-risk)
  2. Upgrade ESLint to v10 (eslint, @eslint/js, eslint-plugin-react-hooks together in one PR)
  3. Address any new lint errors uncovered by stricter react-hooks rules

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions