fix(nf): add support for tailwind 4 with only postcssconfig file - #965
Conversation
|
This PR fixes the lint error causing the pipeline to fail. |
|
Hi @JGhignatti, I appreciate the work you've put in these PR's. I'll take a look! |
|
Hi @Aukevanoost thanks for your help here and all around this project. |
|
Hi @JGhignatti, Yeah I'd say so, but unfortunately no promises and it might take a bit. We're processing some other PR's as well. |
|
No problem. I'll keep an eye open for new versions, and new issues I can help on. Thanks again @Aukevanoost. |
|
Hey @JGhignatti, Just wanted to tell you that I think the next release might take a little longer. I'm aiming for half December. Sorry for the inconvenience |
|
Hi @JGhignatti, hope you're alright It seems like your PR broke something on this issue, would you mind taking a look if we're missing something? Thanks a bunch in advance |
While creating the plugin options passed to ESBuild, only the TailwindCSS config file was being used.
With TailwindCSS v4, it is possible to have a setup without a
tailwind.config.jsfile, only a.postcssrc.jsonfile. The PostCSS config is now used if present, the same way as Angular does.Closes #964