Skip to content

chore(deps): migrate eslint to 8.57.1 #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

MikeMcC399
Copy link
Contributor

@MikeMcC399 MikeMcC399 commented Jul 12, 2025

Situation

npm install fails due to ESLint-related dependency issues (see #18)

The dependencies used for ESLint are all outdated. [email protected], released Feb 13, 2019, is not compatible with Node.js 22. eslint-plugin-mocha@^10 is required.

Package Version Status Latest
eslint 5.14.1 End-of-life 2019-12-21 9.x
eslint-plugin-cypress-dev 2.0.0 Deprecated & Archived 5.0.0
eslint-plugin-mocha 5.3.0 Node.js 22 and flat config unsupported 11.1.0
prettier-eslint-cli 4.7.1 8.0.1

Change

Package From To Package To Version
eslint 5.14.1 same 8.57.1
eslint-plugin-cypress-dev 2.0.0 @cypress/eslint-plugin-dev 6.0.0
eslint-plugin-mocha 5.3.0 same 10.5.0
- - eslint-plugin-json-format 2.0.1
prettier-eslint-cli 4.7.1 same 8.0.1

Note: the highest version of ESLint currently supported by @cypress/eslint-plugin-dev is eslint^8.0.0. This version of ESLint reached end-of-life on Oct 10, 2024.

@MikeMcC399 MikeMcC399 marked this pull request as ready for review July 12, 2025 08:55
@MikeMcC399 MikeMcC399 marked this pull request as draft July 12, 2025 18:26
@MikeMcC399 MikeMcC399 marked this pull request as ready for review July 12, 2025 18:49
update
eslint to 8.57.1
eslint-plugin-mocha to 10.5.0
prettier-eslint-cli to 8.0.1

migrate
eslint-plugin-cypress-dev to @cypress/eslint-plugin-dev 6.0.0

add
eslint-plugin-json-format 2.0.1
@MikeMcC399 MikeMcC399 marked this pull request as draft July 14, 2025 09:54
@MikeMcC399
Copy link
Contributor Author

Put in draft because several upcoming PRs are going to conflict with each other due to proximity of changes in package.json
They need to be prioritized and then rebased each time one of them is merged.

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.

1 participant