no such file or directory, open `'[...]/dist/css/preflight.css'`

[trapfether]

no such file or directory, open `'[...]/dist/css/preflight.css'`

[kg-currenxie]

Same here

[intrepidws]

Samesies

[Trapfether]

I'm looking into this. It appears that the issue described occurs when no local tailwind config can be found for the file. The extension is meant to use the default tailwind config in this case, but that is not happening as expected. I anticipate I'll have this figured out this week.

If anyone else is encountering this issue that HAS a local tailwind config for the impacted file, please expand on you situation here.

As a temporary work-around for those impacted, you can put a basic tailwind.config.js file at the base directory of your project.

[Trapfether]

Here is the update. The extension was updated to version 3.1.0 today. This fixes the preflight not found exception.

However, The extension requires a local tailwind.config file to function correctly and will show the user an error if none is found. This is so that the extension won't touch workspaces that are not using tailwind at all. I cannot imagine the frustration that would occur if a non-tailwind project suddenly had classes moving around because they accidently overlap with tailwind classes.

This means that in the future if we add options for ordering custom / unknown classes (the current behavior is that custom classes are left in their current order) we won't accidently stomp all over someone's non-tailwind project because they flipped that switch globally.

You can use a dummy config file and include it in your .gitignore if you're just looking for local functioning and don't want to include the tailwind config in your repo for some reason.

I will leave this issue open for a few days in case people want to respond to how I went about this. If you have any feedback, I'd be glad to hear it.