[Snyk] Security upgrade eslint from 8.11.0 to 9.4.0

[earthiverse]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

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 @earthiverse, 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 updates the project's eslint dependency to version 9.4.0 to fix a reported security vulnerability. This is a major version upgrade for ESLint, which involves significant changes to its internal dependencies and structure, as detailed in the lock file.

Highlights

• Security Upgrade: This PR was automatically generated by Snyk to address a low-severity Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-BRACEEXPANSION-9789073) by upgrading the eslint dependency.
• Major Version Bump: The eslint dependency is being upgraded from version 8.11.0 to 9.4.0. This is a significant major version jump and likely includes breaking changes and substantial internal restructuring, as reflected in the package-lock.json changes.
• Dependency Updates: The upgrade of eslint necessitates updates and changes to numerous nested dependencies within package-lock.json, including core ESLint components and parsing libraries.

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, automatically generated by Snyk, upgrades eslint from v8.11.0 to v9.4.0 to address a security vulnerability (ReDoS in brace-expansion).

While the direct dependency update is straightforward, this is a major version upgrade for ESLint, which introduces significant breaking changes and requires careful attention:

1. @typescript-eslint Compatibility: The most critical concern is the compatibility of your existing @typescript-eslint/eslint-plugin (^5.16.0) and @typescript-eslint/parser (^5.16.0) with ESLint 9. These versions are not officially compatible. You will likely need to upgrade them to typescript-eslint v6.x (which supports ESLint 9 with flat config) or v7.x (which fully supports ESLint 9). Without this, your TypeScript linting may break or behave unexpectedly.
2. ESLint 9 Breaking Changes:
   • Configuration System: ESLint 9 defaults to the new "flat config" system (using eslint.config.js). If your project uses the legacy .eslintrc.* files, you may need to migrate your configuration or make adjustments.
   • Rule Changes: Some core rules may have been removed or changed.
3. Node.js Version Requirement: ESLint 9 requires Node.js ^18.18.0 || ^20.9.0 || >=21.1.0. Please ensure your project's development and deployment environments meet this requirement. This is reflected in the updated package-lock.json.

Recommendations:

• Upgrade @typescript-eslint: Before merging, or immediately after, update @typescript-eslint/eslint-plugin and @typescript-eslint/parser to versions compatible with ESLint 9.
• Review ESLint Migration Guide: Consult the official ESLint migration guide for v9.
• Thorough Testing: After addressing compatibility and configuration, run your linting tasks and full test suite to catch any issues.

This upgrade is important for security, but due to the major version jump, careful integration is necessary.

[gemini-code-assist]

The upgrade of ESLint to v9.4.0 is a major version change that introduces breaking changes and potential compatibility issues.

Key considerations for this update:

1. @typescript-eslint Compatibility: The current versions of @typescript-eslint/eslint-plugin (^5.16.0) and @typescript-eslint/parser (^5.16.0) are not officially compatible with ESLint 9. These packages will likely need to be upgraded to typescript-eslint v6.x or v7.x to ensure proper functionality. Please verify compatibility and update these dependencies accordingly. This is crucial as Snyk's automated PR might not handle ecosystem dependencies.
2. ESLint Configuration Changes: ESLint 9 defaults to a new flat configuration system (eslint.config.js). If your project uses the legacy .eslintrc.* format, you may need to migrate your configuration or make adjustments to ensure it works correctly with ESLint 9.
3. Node.js Version Requirement: ESLint 9 has updated its Node.js version requirements to ^18.18.0 || ^20.9.0 || >=21.1.0. Ensure your project's development and CI/CD environments meet this new requirement.

After addressing these points, especially the @typescript-eslint upgrade, a full npm install (or equivalent) and thorough testing of your linting setup are highly recommended.

[gemini-code-assist]

This package-lock.json update reflects the upgrade to ESLint 9.4.0 and its associated dependency changes.

A significant change to note within this block is the updated Node.js engine requirement for ESLint itself (line 1493: "node": "^18.18.0 || ^20.9.0 || >=21.1.0").

Please ensure that all development, testing, and deployment environments for this project are compatible with this Node.js version. Running on an older, incompatible Node.js version could lead to runtime errors or unexpected behavior with ESLint 9.