- Issue created by @lauriii
- ๐ซ๐ฎFinland lauriii Finland
Maybe the reason this wasn't working was because I was calling
@import "tailwindcss";
. - ๐ซ๐ฎFinland lauriii Finland
Yep, confirmed this was because of the @import. Not sure if this should be triggering an error. Retitling and reducing priority.
- ๐ณ๐ฑNetherlands balintbrews Amsterdam, NL
The
@import
directive is not implemented intailwindcss-in-browser
, all necessary imports are done automatically. See: https://github.com/balintbrews/tailwindcss-in-browser?tab=readme-ov-file.... Nevertheless, the error message suggests that it might be easy to handle this gracefully and/or give a more explicit error message. - Assigned to balintbrews
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
๐ Compile Tailwind CSS globally for code components Active recently landed.
Is this still relevant?
- ๐ณ๐ฑNetherlands balintbrews Amsterdam, NL
Yes, that issue didn't affect what's being reported here. So this issue is still relevant.
How relevant? Our starter code component code explicitly says "Do not include @import 'tailwindcss'", and it also demonstrates how Tailwind CSS just works without that, so I recommend we change the priority to minor. ๐
Lauri, please bump it back in case you disagree.