New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESM PostCSS configs option #209
Comments
This is great news! Thank you for the heads up — I wouldn't have heard about this without it! |
Bumping this up. |
correct me if i'm wrong, but this will allow using ESM for Tailwind config now too? so both |
It turns out that Vite itself has to be updated to support ESM PostCSS configs (because it doesn't use |
We have to wait for Tailwind themselves to update both their library (PostCSS plugin) and IntelliSense extension to support ESM configs; we're not getting it for free with PostCSS supporting ESM configs, unfortunately. |
Ah man that sucks! hopefully they get out some updates soon. I'm hoping there's some open issues on their ends. |
I forgot we can import PostCSS config and give it to Vite without using their loader, so this is a note to self to try that. |
The answer is yes! Since this is a little weird, I'll implement it as an option. |
I just wanted to chime in. From what little I understand, it's not just that a When I have a Or is there a way to do it? Is this even the correct place to ask or should I go to Stackoverflow and pray someone with the actual knowledge responds? |
You're right, Tailwind itself must be updated to support ESM configs. We are however able to write the PostCSS config in ESM, wherein the Tailwind plugin will still use the |
Now that Tailwind CSS supports ESM, we can push this forward! https://tailwindcss.com/blog/tailwindcss-v3-3#esm-and-typescript-support |
postcss-load-config now supports esm configs.
postcss/postcss-load-config#234
After accepting of sveltejs/svelte-preprocess#520 we can update generated config to .js instead of .cjs
The text was updated successfully, but these errors were encountered: