openshift / openshift/networking-console-plugin
Update ESLint and related linting packages (including @typescript-eslint v8 for TypeScript 5.9.x)
Open
@rszwajko is already working on this.
Since Sep 8, 2026.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 40
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 28
Description
Background
PR #371 bumped TypeScript from 5.7.x to 5.9.3. However, the current @typescript-eslint packages (@typescript-eslint/parser and @typescript-eslint/eslint-plugin) are still pinned at v5.62.0, which officially supports TypeScript only up to ~5.1. Running npm run lint currently succeeds but emits an unsupported TypeScript version warning.
This issue tracks a follow-up upgrade of ESLint and all related linting packages.
Packages to update
| Package | Current version | Target |
|---|---|---|
@typescript-eslint/eslint-plugin |
^5.62.0 |
v8.39.0+ |
@typescript-eslint/parser |
^5.62.0 |
v8.39.0+ |
eslint |
^8.57.1 |
latest (v9.x) |
eslint-config-prettier |
^8.10.0 |
latest |
eslint-plugin-cypress |
^2.15.1 |
latest |
eslint-plugin-perfectionist |
^2.6.0 |
latest |
eslint-plugin-prettier |
^5.1.3 |
latest |
eslint-plugin-react |
^7.34.0 |
latest |
eslint-plugin-react-hooks |
^4.6.0 |
latest |
eslint-plugin-simple-import-sort |
^12.0.0 |
latest |
Notes
@typescript-eslintv8 requires ESLint 8.56.0+ or ESLint 9.x; upgrading to ESLint 9 (flat config) is the recommended path.- ESLint 9 introduces a new flat config format (
eslint.config.js). The existing.eslintrc-based config will need to be migrated. - All
eslint-plugin-*packages should be checked for ESLint 9 /@typescript-eslintv8 compatibility before upgrading.
References
- PR #371 (dependency update for Console 4.22): https://github.com/openshift/networking-console-plugin/pull/371
- Review comment: https://github.com/openshift/networking-console-plugin/pull/371#discussion_r3102902210
- Requested by: @vojtechszocs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.