chore(deps): upgrade tailwind to v4 #1023
Conversation
|
It seems like the problem is the prefix: I couldn't figure out how to set the prefix without importing the preflight at the same time. And having Bulma use the same layers as tailwind does not seem to make things simpler. Given how little we're using tailwind, maybe it's easier to just remove it? Or remove bulma? |
|
So preflight is necessary for prefix? That seems like a bug, no? |
|
Looks like it, but it might be interfering with how we use Bulma. |
| @layer theme, utilities; | ||
|
|
||
| @import "tailwindcss/theme.css" layer(theme) prefix(tw); | ||
| @import "tailwindcss/utilities.css" layer(utilities) prefix(tw); |
There was a problem hiding this comment.
Why didn't you import base and components?
/*
** see discussion under:
** [tailwindlabs/tailwindcss#17594 (comment)](https://github.com/tailwindlabs/tailwindcss/discussions/17594?utm_source=chatgpt.com#discussioncomment-12752302)
*/
@layer theme, base, components, utilities;
@import "tailwindcss/theme.css" layer(theme) prefix(tw);
@import "tailwindcss/utilities.css" layer(utilities);There was a problem hiding this comment.
I tried, but it does not seem to make a difference
There was a problem hiding this comment.
What exactly is the issue?
There was a problem hiding this comment.
Looks broken when adding it, looks broken when not adding it.
No description provided.