You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am the author of said changes and I see it the same as you ^^, having multiple configs which override each other always will result in complexity. My changes fixed issues for some users, but as we now see, resulted in new questions. We really should think about how we can make a module config which is obvious for as many users as possible. Then we can do it as an official breaking change with a major release...
About your config: did you ever try to just do it like this? 😅
postcss({
extract: true,
use: ['sass'],
}),
autoModules, which enables modules for prefixed files, already is enabled by default.
I am using version 3.1.8 and had great trouble getting a css file to avoid getting hashed by the module code.
I have a
transition.css
.My config was this:
I had to log this code to work it out even though I read #292 #296
I ended up eventually with this
It never occurred to me that modules: false would be the answer or autoModules would not apply to everything.
Should there not just be 1 boolean field and that is it?
{ modules: boolean }
I don't know the history and apologies if this comes across rude as this is not my intent.
The text was updated successfully, but these errors were encountered: