[Snyk] Fix for 1 vulnerabilities

[rvu-snyk]

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

Snyk changed the following file(s):

• packages/koa-tracer/package.json
• packages/koa-tracer/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Infinite loop SNYK-JS-BRACEEXPANSION-15789759	641

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.

[rvu-snyk]

This update includes major version upgrades for both eslint and jest, introducing significant breaking changes that will require code and configuration modifications.

eslint@9.39.3 → eslint@10.0.0

This is a high-risk upgrade that requires a mandatory migration of your configuration.

Key Breaking Changes:

• Configuration Overhaul: Support for the traditional .eslintrc configuration file format has been completely removed. You must migrate to the eslint.config.js flat config format.
• Node.js Version: Support for Node.js versions below 20.19.0 has been dropped.
• API for Plugins: Several deprecated context and SourceCode methods have been removed, which may break custom rules or plugins.
• JSX Scope Analysis: JSX reference tracking is now enabled by default, which could lead to new no-unused-vars or no-undef errors in React/JSX projects.

Recommendation: Follow the official ESLint v10 Migration Guide to update your configuration files and resolve potential new linting errors. This is a significant change that must be addressed before merging.

jest@29.7.0 → jest@30.0.0

This is a high-risk upgrade that will likely require changes to your test files.

Key Breaking Changes:

• Node.js Version: Support for Node.js versions 14, 16, 19, and 21 has been dropped. The minimum required version is now 18.
• Matcher Aliases Removed: Deprecated expect matcher aliases have been removed (e.g., toBeCalled() is now toHaveBeenCalled()). An autofixer is available via eslint-plugin-jest.
• Snapshot Updates: The snapshot format has changed, and all snapshots will need to be regenerated.
• DOM Environment: The jest-environment-jsdom package was upgraded, which may introduce subtle changes in behavior for DOM-based tests.
• TypeScript Version: The minimum required TypeScript version is now 5.4.

Recommendation: Run the autofixer from eslint-plugin-jest to update deprecated matchers, and then run your test suite with --updateSnapshot to regenerate all snapshots. Review the official Jest 30 Upgrade 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.