Replies: 1 comment 1 reply
-
Could you provide a git repo that reproduces the unexpected behavior please? As an aside Tailwind isn't meant to be used with Sass. |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
I'm facing an issue after updating from v3 to v4.0.9.
I run tailwind via the postcss plugin in webpack. This is a minimal example to make it reproducible:
webpack.config.js
test.html
test.scss
Please note i use the prefix "tw".
This produces a JavaScript file instead of a CSS File. Normally there is also MiniCssExtractPlugin involved, but to avoid any other influence i removed it.
If i now run
npm exec webpack build -- --mode=development
, thedist/test.js
contains:.tw\\:invisible { visibility: hidden; }
.But running
npm exec webpack build -- --mode=production
it does neither contain the invisible class nor any tailwind related content.Not sure if this is a bug or if i just do some config mistake here.
When i remove the prefix from the test.scss and test.html i get a warning during the compilation
.... but the resulting js file contains a the required class.
Beta Was this translation helpful? Give feedback.
All reactions