[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-access/package.json
• packages/koa-access/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650	721

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 release includes major version upgrades for @babel/cli, eslint, and jest, each introducing significant breaking changes that require developer action. The overall risk is high due to the fundamental nature of these changes, which affect project configuration, code, and runtime environments.

Top Breaking Changes

1. eslint 9.39.4 → 10.0.0 (HIGH RISK)
This upgrade finalizes the transition to the new "flat config" system. Legacy .eslintrc configuration files are no longer supported and must be migrated to eslint.config.js.

• Action Required: Manually migrate your ESLint configuration from .eslintrc.js to the new eslint.config.js format. ESLint provides a migration tool (npx @eslint/migrate-config) to assist with this.
• Node.js Requirement: Support for Node.js versions below 20.19.0 has been dropped.
• Configuration Loading: The algorithm for locating eslint.config.js has changed, which may affect monorepos.

2. @babel/cli 7.28.6 → 8.0.0 (HIGH RISK)
Babel 8 modernizes its core, which impacts project setup and build configurations significantly. It is now ESM-only and targets modern environments by default.

• Action Required: Update your Babel configuration (babel.config.js) to align with the new defaults. The most significant change is that @babel/preset-env no longer compiles code to ES5 by default.
• Node.js Requirement: Babel 8 itself requires Node.js 22 or newer to run.
• ESM-Only: Babel now ships as ESM packages.
• Polyfills: Polyfill injection has been extracted to separate packages, and the useBuiltIns option has been removed.

3. jest 29.7.0 → 30.0.0 (MEDIUM RISK)
Jest 30 introduces several breaking changes, but many can be handled with automated tools. The primary impact is on environment compatibility and test code syntax.

• Action Required: Run a codemod or use eslint-plugin-jest with its autofixer to replace removed matcher aliases (e.g., toBeCalled() becomes toHaveBeenCalled()). Snapshots will also need to be updated.
• Node.js Requirement: Support for Node.js 14, 16, 19, and 21 has been dropped.
• TypeScript Requirement: The minimum required TypeScript version is now 5.4.

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