[Snyk] Security upgrade eslint from 8.18.0 to 9.0.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	436

---

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, aims to enhance the project's security posture by updating a key development dependency, eslint, to a version that mitigates a known vulnerability. It's a straightforward dependency bump, but requires a follow-up manual step to ensure consistency in the dependency tree.

Highlights

• Security Upgrade: This pull request addresses a Regular Expression Denial of Service (ReDoS) vulnerability by upgrading the eslint dependency.
• Dependency Update: The eslint development dependency has been upgraded from version 8.18.0 to 9.0.0.
• Manual Intervention Required: The package-lock.json file was not automatically updated and requires manual intervention to be updated before merging this pull request.

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 configure Gemini 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, automatically generated by Snyk, upgrades ESLint to version 9.0.0 to resolve a security vulnerability. While the change is simple, it's a major version upgrade with significant breaking changes. My review highlights the critical need to update the package-lock.json file and provides guidance on migrating to ESLint v9 to avoid breaking your linting setup.

[gemini-code-assist]

As noted in the pull request description, package-lock.json has not been updated. This is a critical step that needs to be completed before merging.

Without an updated lockfile:

• The vulnerability Snyk is trying to fix might not actually be resolved in your deployment or CI environments, as they often use npm ci which relies on the lockfile.
• Other developers running npm install might get inconsistent dependency versions.

Please run npm install to generate the updated package-lock.json and commit it to this branch.

[gemini-code-assist]

This pull request upgrades ESLint from version 8 to 9. This is a major version bump that includes significant breaking changes which could affect your project's linting setup.

Key changes to be aware of include:

• New Config System: ESLint v9 uses eslint.config.js by default and has deprecated the older .eslintrc.* configuration files.
• Node.js Version: Support for Node.js versions older than 18.18.0 has been dropped.
• Rule Changes: Some core rules have been removed or modified.

I strongly recommend reviewing the official ESLint v9 migration guide to ensure a smooth transition and update your configuration accordingly to prevent breaking your linting process.