Clarification of tailwindcss configuration

[TheDavidFactor]

I see assets/tailwind.config.js exists, but according to the .js file is legacy and won't be used unless the @config directive is used to load it. I do not see a corresponding directive in assets/css/app.css so am I correct in assuming the tailwind.config.js is a legacy artifact and can be deleted?

[nickjj]

Hi,

I recall running into issues getting PostCSS to work with the new CSS directives but if you're open to testing that out and confirming it still works without it, I'm game for changing.

[TheDavidFactor]

I'm no expert, your work and this project have been my introduction to css pre-processing and extensions. I've removed it from my project and nothing has broken, but I wouldn't take that to mean a whole lot. I asked the question more for my own knowledge and understanding.

[nickjj]

I think a good test here would be to write custom CSS that exercises some of PostCSS' features. This project gives you an empty slate so I think it's expected it still works when removed.