-
Type:
Sub-task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a mongodb node driver developer
I want to use the latest major version of eslint (v10) in dbx-js-tools
So that compatible plugins and dependent packages can be updated, promoting maintainability
User Experience
- eslint checks should pass with the same rule parity following the v9 non-flat configuration file
Dependencies
- The flat config migration for dbx-js-tools (the "[dbx-js-tools] update eslint to use flat config" sibling subtask), because eslint v10 only reads eslint.config.* files.
Risks/Unknowns
- A simple transition could cause a lack of parity with v9 rules (e.g: an added rule in v10 which supplants a rule in v9)
- Dissimilar linting between repos
- Other plugin incompatibility discoveries (prettier, tsdoc, simple-import-sort, etc)
Acceptance Criteria
Implementation Requirements
- Bump eslint to ^10 in the root package.json and update package-lock.json.
- After this change, npm run check:eslint should pass.
- Remove the eslint ignore (versions >=10.0.0) from .github/dependabot.yml.
- Consider extending the paths filter in .github/workflows/lint.yml to cover package.json, package-lock.json and the eslint config, so dependency bumps run lint. The eslint 10 bump (PR #65) merged without a lint run because the workflow only triggers on packages/**.
Testing Requirements
- Compare verbose output of eslint checks before and after the upgrade, ensure all files are covered
- Smoke test rule changes to ensure they are actually emitting errors/warns
Documentation Requirements
n/a
Follow Up Requirements
n/a