[Snyk] Security upgrade eslint from 8.18.0 to 9.4.0

[nn6n]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	508

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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)

[gemini-code-assist]

Summary of Changes

Hello @nn6n, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, updates the eslint development dependency to a newer version to address a security vulnerability. The primary change is the version number update in package.json.

Highlights

• Dependency Upgrade: Upgraded the eslint dependency from version 8.18.0 to 9.4.0 in the devDependencies section of package.json (specifically on line 18).
• Security Fix: This version bump is intended to fix a reported Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-BRACEEXPANSION-9789073) associated with the older version.
• Manual Step Required: Snyk reported that it failed to update the package-lock.json file, which will need to be updated manually before merging this PR.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades ESLint from version 8.18.0 to 9.4.0, primarily to address a security vulnerability. This is a positive step for project security.

Crucial Actions Before Merging:

1. Update Lock File: The pull request description correctly notes that package-lock.json was not automatically updated. Please ensure you regenerate and commit the updated package-lock.json (typically by running npm install after this change and then committing the lock file). This step is essential for ensuring dependency consistency and reproducible builds for all developers and CI environments.

2. Verify ESLint v9 Compatibility: This upgrade moves ESLint from v8 to v9, which is a major version change. Such updates often come with breaking changes that could affect your project's linting rules, configurations, or plugins. It is strongly recommended to:

   • Thoroughly test your project's linting functionality after applying this change.
   • Review your ESLint configuration files (e.g., .eslintrc.js, .eslintrc.json) and any custom plugins or shareable configs for compatibility with ESLint v9.
   • Refer to the official ESLint v9 migration guide for detailed information on breaking changes and how to adapt your project.

Addressing these points will help ensure a smooth and secure upgrade, maintaining code quality and development workflow.

[gemini-code-assist]

Upgrading ESLint to a new major version (v8.x to v9.x) is a significant update. Major versions can introduce breaking changes that might affect your current linting setup. It's important to:

• Verify that your ESLint configurations (e.g., .eslintrc.*, eslint.config.js) are compatible with ESLint v9.
• Check if the versions of your ESLint plugins and configurations (like [email protected] and [email protected], which are also listed as devDependencies) are compatible with ESLint v9. They might also require updates for compatibility.
• Thoroughly test the linting process across your codebase (e.g., by running your lint script or npx eslint .) to identify and address any new errors or unexpected behavior.
• Consult the official ESLint v9 migration guide for detailed information on changes and recommended upgrade steps.