[Snyk] Security upgrade eslint from 8.57.1 to 10.0.0 - #289
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-AJV-15274295
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Summary
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee1fd8f8f7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "concurrently": "^8.2.2", | ||
| "dts-bundle-generator": "^9.3.1", | ||
| "eslint": "^8.57.0", | ||
| "eslint": "^10.0.0", |
There was a problem hiding this comment.
Keep ESLint version compatible with TypeScript ESLint
Upgrading eslint to ^10.0.0 while leaving @typescript-eslint/eslint-plugin and @typescript-eslint/parser at ^7.4.0 (package.json lines 62-63) introduces a peer-dependency mismatch that can break dependency resolution in standard installs (e.g., npm install/CI) and blocks lint tooling. This regression is introduced by the new eslint range on line 68 and should be paired with a compatible @typescript-eslint/* major upgrade (or kept on the prior ESLint major).
Useful? React with 👍 / 👎.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-AJV-15274295
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)