[Snyk] Upgrade tailwindcss from 3.4.14 to 3.4.18

[sestinj]

Snyk has created this PR to upgrade tailwindcss from 3.4.14 to 3.4.18.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 4 versions ahead of your current version.

• The recommended version was released 2 months ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Command Injection SNYK-JS-GLOB-14040952	436	Proof of Concept
	Prototype Pollution SNYK-JS-JSYAML-13961110	436	No Known Exploit
	Directory Traversal SNYK-JS-VITE-13644406	436	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	436	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	436	Proof of Concept
	Relative Path Traversal SNYK-JS-VITE-12558116	436	Proof of Concept

Release notes

Package name: tailwindcss

• 3.4.18 - 2025-10-01
  

  Fixed

  • Improve support for raw supports-[…] queries in arbitrary values (#13605)
  • Fix require.cache error when loaded through a TypeScript file in Node 22.18+ (#18665)
  • Support import.meta.resolve(…) in configs for new enough Node.js versions (#18938)
  • Allow using newer versions of postcss-load-config for better ESM and TypeScript PostCSS config support with the CLI (#18938)
  • Remove irrelevant utility rules when matching important classes (#19030)
• 3.4.17 - 2024-12-17
• 3.4.16 - 2024-12-03
• 3.4.15 - 2024-11-14
• 3.4.14 - 2024-10-15

from tailwindcss GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Summary by cubic

Upgrade tailwindcss to 3.4.18 in the VS Code extension to pick up security fixes and Node 22+ compatibility improvements. No code changes beyond package.json.

• Dependencies
  • Bump tailwindcss from ^3.3.2 to ^3.4.18.

^{Written for commit 47501ee. Summary will update automatically on new commits.}

[continue]

Keep this PR in a mergeable state →

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

[continue-development-app]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

[continue-development-app]

Keep this PR in a mergeable state →

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ AI review failed. Please check the Continue API key and configuration.

Troubleshooting

• Verify the CONTINUE_API_KEY secret is set correctly
• Check that the organization and config path are valid
• Ensure the Continue service is accessible

---

[cubic-dev-ai]

No issues found across 1 file

[continue]

The CI failure was due to package-lock.json being out of sync with package.json. I've opened #9114 to fix this issue by updating the lock files.