J

Hi, sorry about this issue everyone. I had attempted a fix for it a few days ago but there were other problems with the implementation I chose, so I have...

All you need is a MambaScript to JavaScript compiler (that can be called from JavaScript). Try experimenting in a SvelteKit project wherein you configure `svelte-preprocess` and Vite as necessary: https://github.com/sveltejs/svelte-preprocess/blob/main/docs/preprocessing.md#custom-preprocessors...

Good idea. The current note > This is an adder for `svelte-add`; you should [read its `README`](https://github.com/svelte-add/svelte-add#readme) before continuing here. might not make issues as discoverable as they should be.

You can do whatever you want to create a schema. See the comment in `src/graphql/schema.ts`. You can also use whatever GraphQL client you want. (I personally just use `fetch`).

This is great news! Thank you for the heads up — I wouldn't have heard about this without it!

It turns out that Vite itself has to be updated to support ESM PostCSS configs (because it doesn't use `postcss-load-config`) before we can use them in our projects. 😞

> correct me if i'm wrong, but this will allow using ESM for Tailwind config now too? so both `tailwind.config.js` and `postcss.config.js` will be **JavaScript** files and not **CommonJS** ?...

I forgot we can import PostCSS config and [give it to Vite](https://vitejs.dev/config/#css-postcss) 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.

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...