Just a heads up for people using tailwind with babel plugin macros (as per Tailwindcss with babel-macro-plugin and CSS-in-JS - #38 by jeffceriello)
It seems config / css output is getting cached somewhere
I make changes to tailwind.config.js (adding some responsive utilities for my global styles) and build my tailwind.css to index.css
I then import the index.css into my theme as a Global style
I’m also using twin.macro which I guess is also creating its own versions of my utility classes because I use eg
For some reason, any changes to the tailwind config / built css don’t update on the front end. Even after a complete rebuild. The index.css itself has the new values, but when I run my site it’s getting old values for the css in server.js
I tried deleting my build folder. I tried rebuilding my css. Deleted my app data in my browser. Ran in incognito. I restarted VS Code etc. I restarted Wamp
Eventually something updated it, but I’m not sure what.
Again what’s odd is the index.css is updated fine but it’s not getting updated into server.js correctly .
I’m wondering If this is more an issue with Frontity’s style import rather than tailwind specifically
I guess I can try with a basic index.css etc file, skipping the tailwind part, and see if it still happens
Any advice appreciated