[Snyk] Security upgrade eslint from 8.57.0 to 9.0.0

[Dustin4444]

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
	Prototype Pollution SNYK-JS-JSYAML-13961110	49

---

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:

🦉 Prototype Pollution

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-27233b4f87f468ec937c0b32b89d9d94

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, 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 resolving a 'Prototype Pollution' vulnerability. The primary change involves a version bump for the 'eslint' dependency. While the core dependency update is handled, a manual step is required to update the 'package-lock.json' file to fully integrate the changes and ensure consistency.

Highlights

• Security Vulnerability Fix: This pull request addresses and fixes a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) with a medium severity score of 49.
• Dependency Upgrade: The fix is implemented by upgrading the 'eslint' dependency from version 8.57.0 to 9.0.0 in the 'package.json' file.
• Automated PR by Snyk: This pull request was automatically generated by Snyk to provide an automated security fix.
• Manual Intervention Required: A warning indicates that the 'package-lock.json' file failed to update automatically and requires manual intervention before merging.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 upgrades ESLint from v8 to v9 to address a security vulnerability. This is a major version update which introduces significant breaking changes. It is critical to update the package-lock.json file by running npm install before merging. Additionally, you will need to address the breaking changes from ESLint v9, most notably the new flat configuration system and the updated Node.js version requirement. Please test your linting setup thoroughly after making these changes.

[gemini-code-assist]

This upgrade to ESLint v9 is a major version bump and introduces several critical breaking changes that must be addressed.

1. Update package-lock.json
As noted in the PR description, package-lock.json has not been updated. You must run npm install (or your package manager's equivalent) and commit the resulting changes to package-lock.json to ensure the correct version of eslint is installed.

2. Breaking Changes in ESLint v9
This is a major update with significant changes. Your linting setup will likely break without migration steps. Key changes include:

• New Default Config System (Flat Config): ESLint v9 now uses eslint.config.js (flat config) by default. The previous .eslintrc.* format is no longer supported out-of-the-box. You must either migrate your configuration to the new format or opt-out by setting the ESLINT_USE_FLAT_CONFIG=false environment variable.
• Node.js Version: ESLint v9 requires Node.js ^18.18.0 or >=20.0.0. Please ensure your development and CI/CD environments are updated accordingly.
• Rule Changes: Some rules have been removed from the core and moved to other plugins (e.g., eslint-plugin-jsdoc).

For a comprehensive guide on how to handle these changes, please refer to the official ESLint v9 Migration Guide.

Given the extent of these changes, thorough testing of your linting process is essential after updating.