feat: Upgrades 2025-12, pnpm, tailwinds 4

[richtera]

Ticket ID

Description

[cloudflare-workers-and-pages]

Deploying tools-web-components with    Cloudflare Pages

Latest commit:	39e8d6c
Status:	🚫  Build failed.

View logs

[github-actions]

Storybook deployed with Cloudflare Pages ☁️ 📖 🚀

Storybook

• URL: https://pr-756.tools-web-components.pages.dev
• Specific: https://00349e3c.tools-web-components.pages.dev

Built from commit 044ccd0

[richtera]

This is going to take more time or maybe it won't work. Sass and tailwinds 4 don't seem to work together because sass has a backward compatible @import and tailwinds relies on it being passed to the tailwinds plugin.

[richtera]

The failing cloudflare deployment is fine. We're going to start to deploy using github actions just like the other project once this is merged. This one already does the deployment that way so the URL in the PR comment is correct to check.

[dzbo]

This is going to take more time or maybe it won't work. Sass and tailwinds 4 don't seem to work together because sass has a backward compatible @import and tailwinds relies on it being passed to the tailwinds plugin.

I think we can get rid of SASS since modern css has nesting already, besides we don't write much custom styles anyway

[richtera]

Yea I am only using sass in order to create the old main.css and to allow the -v4 files to share some code. The actual storybook and components should no longer be using sass.