Replies: 1 comment 4 replies
-
It's difficult to help without a minimal repro showing versions and config. In particular, have you tried Docusaurus Faster and the We don't use Tailwind and we haven't created any plugin for it. We can't guarantee third-party plugins we didn't develop work great. Most likely, the v4 future flag issue is related to the introduction of CSS Cascade Layers in v3.8: https://docusaurus.io/blog/releases/3.8#css-cascade-layers We also have a Tailwind-related issue here, maybe you'll find an answer if you post a minimal repro the community can take a look at: #2961 |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Maybe it should be an issue and not a discussion since it seems like a bug, but not sure:
I started using docusaurus, added tailwind and when using
npm run start
everything works great.When I use
npm run build
I get a long warning (see below) that seems related to minifying css, and the output styling looks pretty bad, not as it should.When I removed the tailwind plugin the warning disappeared (that's why I believe its related to tailwind) but obviously site looks bad.
--no-minify
and the issue was solved, no warning and site looks good.Here is the warning:
Beta Was this translation helpful? Give feedback.
All reactions