[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• package.json
• pnpm-lock.yaml

Vulnerabilities that will be fixed with an upgrade:

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

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.

[snyk-io]

This update includes a high-risk major upgrade for eslint and a medium-risk major upgrade for @vscode/vsce.

eslint 8.57.1 → 10.0.0 (High Risk)

This upgrade crosses two major versions (v9 and v10) and introduces significant breaking changes, requiring mandatory migration.

Key Breaking Changes:

• Configuration Overhaul: Support for the traditional .eslintrc.js configuration file is completely removed in v10. You must migrate to the new flat configuration format (eslint.config.js). The ESLINT_USE_FLAT_CONFIG environment variable is no longer supported.
• Node.js Requirement: ESLint v10 requires Node.js version 20.19.0 or newer.
• Removed Functionality: Several command-line flags, formatters, and rules (like valid-jsdoc) have been removed.
• Stricter Behavior: /* eslint-env */ comments are now considered errors and must be replaced with configuration in your eslint.config.js file.

Recommendation:
This is a significant migration effort. Before merging, you must create an eslint.config.js file and translate your existing .eslintrc configuration to the new format. Test thoroughly in your CI/CD environment after updating the Node.js version.

Source: ESLint v9 Migration Guide, ESLint v10 Migration Guide

@vscode/vsce 2.32.0 → 3.9.2 (Medium Risk)

This is a major version upgrade. While no specific API removals or mandatory code changes are documented in the available release notes for the v3.0.0 transition, the risk is classified as medium due to the lack of a detailed changelog for this major boundary. Upgrades across major versions can introduce subtle behavioral changes or drop support for older environments.

Recommendation:
After upgrading, verify that your VS Code extension packaging and publishing workflows (vsce package and vsce publish) continue to function as expected.

Source: Package documentation

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

[snyk-io]

⛔ Snyk checks have failed. 35 issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (35)
⛔	Open Source Security	5	30	0	0	35 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

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