[Snyk] Fix for 2 vulnerabilities

[factory-service-snyk]

Snyk has created this PR to fix 2 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
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18313044	710
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18313070	710

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:

🦉 Allocation of Resources Without Limits or Throttling

[factory-service-snyk]

This update includes major version upgrades for both eslint and @vitest/coverage-v8, introducing significant breaking changes that require developer action.

eslint@9.39.4 → eslint@10.0.0

Risk: HIGH

This is a major upgrade with substantial breaking changes. Action is required to migrate your configuration.

• Configuration Format: Support for the legacy .eslintrc file format has been completely removed. You must migrate to the "flat config" format (eslint.config.js).
• Node.js Support: Support for Node.js versions older than v20.19.0 has been dropped.
• JSX Scope Analysis: ESLint now properly tracks JSX references, which may result in new linting errors for unused component imports.
• eslint-env Comments: The use of /* eslint-env */ comments is no longer supported and will cause an error.

Recommendation: Follow the official ESLint v10 Migration Guide to update your configuration files and resolve new linting errors.

@vitest/coverage-v8@3.2.4 → @vitest/coverage-v8@4.0.0

Risk: HIGH

This upgrade is part of the Vitest v4 release and introduces breaking changes related to environment support and configuration.

• Environment Requirements: Vitest v4 now requires Node.js >= 20.0.0 and Vite >= 6.0.0.
• Coverage Configuration: The coverage.all option has been removed. To include uncovered files in your coverage report, you must now explicitly define the coverage.include option in your configuration.
• Coverage Accuracy: The V8 coverage provider uses a new, more accurate AST-based method for remapping results. Expect to see changes in your coverage reports.
• Pool Configuration: The maxThreads and maxForks options have been replaced with maxWorkers.

Recommendation: Update your Vitest configuration to set coverage.include to maintain previous coverage reporting behavior and update pool settings if you use them. Ensure your Node.js and Vite versions meet the new requirements. Review the Vitest v4 Migration Guide for a complete list of changes.

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