[Snyk] Security upgrade eslint from 4.19.1 to 9.26.0#43
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-ESLINT-15102420
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e17df61789
ℹ️ 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".
| "chalk": "^2.4.1", | ||
| "cross-spawn": "^5.1.0", | ||
| "eslint": "^4.19.1", | ||
| "eslint": "^9.26.0", |
There was a problem hiding this comment.
Align Node engine with ESLint 9 requirements
This bump pulls in ESLint 9, but packages/scripts/package.json still advertises engines.node >=8 (line 21), so consumers on Node 8–17 will now hit install/runtime failures because ESLint 9 no longer supports those Node versions. That’s a breaking compatibility regression for the package as currently declared; either keep ESLint on a version compatible with Node 8+ or update the engine range to match ESLint’s minimum supported Node version.
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):
packages/scripts/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-ESLINT-15102420
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:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.