[Snyk] Fix for 2 vulnerabilities

[hnejra]

Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• packages/pluggable-widgets-tools/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled Recursion SNYK-JS-BRACES-19963945	721
	Infinite loop SNYK-JS-URIJS-19963963	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:

🦉 Uncontrolled Recursion

[hnejra]

This release includes major version upgrades for both eslint and babel-jest, introducing significant breaking changes that require developer action.

eslint@9.39.4 → eslint@10.0.0

Risk: HIGH

The upgrade to ESLint v10 is a major breaking change that requires mandatory configuration updates.

Key Breaking Changes:

• Configuration System Removal: The legacy .eslintrc configuration format has been completely removed. All projects must migrate to the eslint.config.js (flat config) format. ESLint provides a migration script to assist with this transition.
• Node.js Support: Support for Node.js versions older than v20.19.0 has been dropped.
• New Config Lookup: The algorithm for finding the configuration file has changed. It now searches up from the directory of each linted file, which is a notable change for monorepos.
• API & Rule Changes: Several deprecated API methods have been removed, which may affect custom rules or plugins. Additionally, the eslint:recommended ruleset has been updated, and JSX scope analysis is improved, which could lead to new linting errors.

Recommendation: Before merging, run the official migration script (npx @eslint/migrate-config) to convert your configuration to the new format. Review the generated eslint.config.js and test your linting setup thoroughly. Ensure your development and CI/CD environments are using a compatible Node.js version (v20.19.0+).

babel-jest@29.7.0 → babel-jest@30.3.0

Risk: HIGH

This upgrade is part of the larger Jest v30 release, which contains several breaking changes that will likely require code and environment updates.

Key Breaking Changes:

• Node.js Support: Jest 30 drops support for Node.js 14, 16, 19, and 21.
• Removed Matcher Aliases: Deprecated expect aliases have been removed (e.g., toBeCalled()). Code must be updated to use the canonical names (e.g., toHaveBeenCalled()). The eslint-plugin-jest package provides an autofixer for this.
• Snapshot Updates: The format for snapshots has changed, which will require you to update your existing snapshots.
• JSDOM Upgrade: The bundled jest-environment-jsdom has been significantly upgraded, which may cause subtle behavior changes in tests that rely on specific DOM APIs.
• TypeScript Version: The minimum supported TypeScript version is now 5.4.

Recommendation: Plan to run your entire test suite after upgrading. Use the eslint-plugin-jest autofixer to handle removed aliases and be prepared to update all snapshots. Verify that your project's Node.js version meets the new requirements.

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