fix: actually run CI actually on ESLint 10#609
fix: actually run CI actually on ESLint 10#609controversial wants to merge 1 commit intomdx-js:masterfrom
Conversation
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #609 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 19 19
Lines 273 273
Branches 53 51 -2
=========================================
Hits 273 273 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ESLint 10 was added to the CI matrix in #602 but due to a conditional in the CI step that actually installs eslint
eslint-mdx/.github/workflows/ci.yml
Lines 45 to 48 in f717ff2
it was never installed and the tests did not actually run on that ESLint major version
The tests do not pass on ESLint 10 when they’re actually run there, notably because:
eslint-plugin-reactdoes not support ESLint 10 (used in testing configs)@typescript-eslint/utilsthat’s installed via@1stg/common-configdoes not support ESLint 10I would probably recommend
typescript-eslintpackages in CI when ESLint 10 is runningeslint-plugin-reactto the more modern & maintained@eslint-react/eslint-pluginI don’t have time to do this migration work myself to make the tests pass so I will mark this PR back to draft
Initial checklist