Skip to content

chore(deps): Remove unused typescript-eslint plugin - #1305

Merged
gabrielcld2 merged 1 commit into
developfrom
chore/remove-typescript-eslint-plugin
Oct 5, 2026
Merged

gabrielcld2 merged 1 commit into
developfrom
chore/remove-typescript-eslint-plugin

Conversation

@utkarshcloudinary

Copy link
Copy Markdown
Collaborator

Supersedes #1292.

Approach

  • Remove @typescript-eslint/eslint-plugin from devDependencies. The project has no TypeScript and eslint.config.js does not reference it.
  • @wordpress/eslint-plugin still installs it through typescript-eslint, with a parser version that matches, so lint behavior does not change.
  • The direct entry caused chore(deps-dev): bump @typescript-eslint/eslint-plugin from 8.65.0 to 8.70.1 #1292: Dependabot bumped only the plugin to 8.70.1, which needs @typescript-eslint/parser@^8.70.1, while typescript-eslint@8.65.0 pins the parser to 8.65.0. npm ci then failed with ERESOLVE.

QA notes

  • npm ci completes without ERESOLVE.
  • npm run lint:js and npm run build complete with no new errors.

The project has no TypeScript and eslint.config.js does not use
@typescript-eslint/eslint-plugin directly. @wordpress/eslint-plugin
already brings it in through typescript-eslint, with a matching
parser version.

The direct entry made Dependabot bump only the plugin, which broke
npm ci with a peer conflict on @typescript-eslint/parser (#1292).
@gabrielcld2
gabrielcld2 merged commit f708f6f into develop Oct 5, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants