I have managed to figure out what was wrong with the compatibility module, it wasn’t liking how I had laid out some stuff in the config file but it wasn’t overly clear about it from the error. But does anyone know if someone plans to pickup the PostCSS module to update it to v8?
A good example of how to set everything up can be found in the Packosphere repository if you still need it.
As far as picking up maintenance of the postcss package, there is an open issue for it being moved to the Meteor-Community-Packages org so that it can be kept up to date by the community. Currently, it works well with Tailwindcss with the minor issue of displaying dependency warnings in the console when you use the most recent versions of postcss and postcss-load-config but these don’t actually affect the build.
When I tried it with the latest versions of all the packages it was throwing errors for me causing the CSS to not compile at all. I ended up reverting to slightly older versions and using the v7 compat build of Tailwinds 2.