[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
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18512280	170

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

[snyk-io]

This upgrade contains a major version update for eslint from v8 to v9, which is a high-risk change with significant breaking changes. The update for @vscode/vsce is a major version jump with unclear changes, representing a medium risk.

eslint@8.57.1 → eslint@9.0.0 (High Risk)

The upgrade to ESLint v9.0.0 introduces substantial breaking changes that require mandatory configuration and environment updates. [1, 3]

Key Breaking Changes:

• New Default Config Format: The "flat config" (eslint.config.js) is now the default. The traditional .eslintrc files are deprecated and will not work without setting an environment variable (ESLINT_USE_FLAT_CONFIG=false). Configuration files must be migrated to the new format. [1, 2, 3]
• Node.js Support: Support for Node.js versions older than v18.18.0 has been dropped. [2, 3]
• Removed Functionality: Several core formatters (including checkstyle, junit, compact) and the valid-jsdoc and require-jsdoc rules have been removed. [2, 3]
• API and Rule Changes: Function-style rules are no longer supported, and there are breaking changes to the Linter API for integrations. [2, 3]

Recommendation:
This upgrade requires a manual migration of your ESLint configuration. Follow the official Migration Guide and use the provided codemods to assist with the transition. [2] This should be handled in a separate, dedicated effort before merging.

@vscode/vsce@2.32.0 → @vscode/vsce@3.9.2 (Medium Risk)

This is a major version upgrade for the Visual Studio Code extension publishing tool. A specific changelog detailing the breaking changes between v2 and v3 was not found. Due to the lack of clear documentation for this major version jump, the risk is assessed as medium. Changes to command-line arguments, configuration, or required Node.js versions are possible and require verification.

Recommendation:
After upgrading, verify your extension packaging and publishing pipeline by running vsce package and vsce publish commands to ensure they complete successfully.

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. 48 issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (48)
⛔	Open Source Security	9	39	0	0	48 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.