[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

This change is 

[snyk-io]

This upgrade includes a major version bump for eslint from v9 to v10, which introduces significant breaking changes. The upgrade for nodemon is a minor patch.

eslint@9.39.3 → eslint@10.0.0

Risk: HIGH

ESLint v10 completely removes the legacy .eslintrc configuration system in favor of the flat config (eslint.config.js) system introduced in v9. It also drops support for older Node.js versions.

Key Breaking Changes:

• .eslintrc Removed: Projects still using .eslintrc.* files must migrate to eslint.config.js. The old format is no longer supported.
• Node.js Version: Support for Node.js versions older than v20.19.0 has been removed.
• Config File Lookup: The logic for finding configuration files has changed to start from the directory of each linted file, which primarily affects monorepos.
• JSX Reference Tracking: ESLint now correctly tracks JSX element references, which may cause new errors to appear with rules like no-unused-vars.

Recommendation:
Before merging, developers must migrate the ESLint configuration from the legacy .eslintrc format to the new eslint.config.js format. The ESLint team provides a migration guide to assist with this process. Ensure your CI and local environments are using a compatible Node.js version (v20.19.0+).

nodemon@3.1.10 → nodemon@3.1.12

Risk: LOW

This is a patch-level update that includes minor bug fixes and dependency updates. No breaking changes are documented.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c83e42d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.