Environments - Tailwinds custom colours failing to load. - upgrading from 4.3.1 > 4.6.2

[landoDanziger]

I've been using different environments for ESPs and for BRANDS.

When upgrading from 4.3.1 . 4.6.2 - custom colours no longer load in components - anyone come across this?

build: {
fail: 'verbose',
tailwind: {
config: 'tailwind-outlet.config.js',
css: 'src/css/outlet-tailwind.css',
},

The colours do work if I write them in the template - but not in components - I will try and learn the new component system - and see if it works there.

Works in 4.3.1

EDITL Actually - i must have dreamt it - I'm not getting any custom tailwinds colours in my builds, regardless of ENV.

[landoDanziger]

I re-wrote all my templates in the new components syntax using chat gpt and co-pilot and it works fine.

I suspect the custom paths I had may have caused an issue, but tbh I am happy to be finally almost up to date in time for the neeeext upgrade. :D

I really love the new components, the script props - it has simplified my shortcode structure no end. Component nesting is working really well, and assigning locally, or through the page.object, with a fallback for dev is working great.

All the stacks pull push stuff seems great too, and a lot more flexible. Will get rid of a few of the barbaric hacks I was using.