[Snyk] Fix for 2 vulnerabilities

[sestinj]

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

Snyk changed the following file(s):

• extensions/vscode/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Infinite loop SNYK-JS-NANOID-18506894	696
	Infinite loop SNYK-JS-NANOID-18506897	696

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.

[sestinj]

This update includes major version upgrades for both tailwindcss and vitest, introducing significant breaking changes that require mandatory configuration and code modifications.

tailwindcss@3.4.14 → tailwindcss@4.0.0

Risk: HIGH

Tailwind CSS v4 is a complete rewrite with a new, much faster engine written in Rust. The primary breaking change is a shift from JavaScript-based configuration to CSS-first configuration.

Key Breaking Changes:

• Configuration File: The tailwind.config.js file is replaced by an @theme block within your main CSS file. While the old config may still function, it is considered a deprecated path.
• Build Integration: The @tailwind directives (@tailwind base, @tailwind components, @tailwind utilities) are replaced by a single @import "tailwindcss";.
• Dependencies: The PostCSS plugin is now a separate package (@tailwindcss/postcss) that must be installed explicitly.
• Removed Utilities: Deprecated utilities like text-opacity-* and flex-grow-* have been removed in favor of their modern replacements.

Recommendation:
Use the official upgrade tool (npx @tailwindcss/upgrade@latest) to automate much of the migration. Carefully review the migration guide to move your theme configuration from tailwind.config.js into your CSS file.

Source: Tailwind CSS v4 Migration Guide

vitest@3.2.3 → vitest@4.0.0

Risk: HIGH

Vitest v4 introduces several significant breaking changes to its configuration, browser mode, and coverage reporting.

Key Breaking Changes:

• Node.js Requirement: The minimum required Node.js version is now 20.0.0.
• Workspace Configuration: The vitest.workspace.ts file and defineWorkspace are removed. Monorepo projects are now defined using a projects array inside the main vitest.config.ts.
• Browser Mode: Browser Mode is now stable but has been completely reworked. You must install separate provider packages (e.g., @vitest/browser-playwright) and update your configuration accordingly. The @vitest/browser package should be removed.
• Coverage Reporting: The coverage.all option now defaults to true, which may cause your coverage numbers to drop if you don't have explicit include patterns configured.
• Removed APIs: Several configuration options deprecated in v3 have been removed, such as poolMatchGlobs, deps.external, and deps.inline.

Recommendation:
Follow the official migration guide carefully. Start by updating your Node.js version and then refactor your configuration to use the new projects structure if applicable. Update your browser mode and coverage settings as required.

Source: Vitest v4 Migration Guide

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