Migration from v3 to v4 crippled whole site design

[bpzr01]

Hi, it looks like the migration did some serious damage to my website. For example container mx-auto, py-* is not working, size-11 is much larger now. Did I miss some mentions about these changes or can it be some other problem?
Tested on Chrome Version 135.0.7049.52 (Official Build) (64-bit) so things like padding-block should be supported.

[wongjn]

You can check the upgrade guide for an overview of changes. Although it could indeed be some other problem.

[bpzr01]

I did and it seems like the internal changes to the tailwind (like the py got changed to the padding-block) are not being picked up, I got no errors whatsoever though. I also used the recommended way of migrating - using the npx /upgrade script.

[wongjn]

The upgrade script is not perfect and does need manual validation of its changes. It seems like there could indeed be some other problems.

[bpzr01]

The issue was caused by using old node version for running the upgrade script and also a default styling behaving differently in v4.