Dominik G.

filed upstream: https://github.com/vitejs/vite/issues/20511

I added dynamicCompileOptions to vite-plugin-svelte a while ago as an experimental option and it was promoted to a stable option since. Because it only works with vite-plugin-svelte it's not on...

can't reproduce this in stackblitz or linux (manjaro, arch based). Does your home path include any special characters or are there other customizations on your fs that could impede the...

So if the content of __vite__css is the whole .svelte file, it looks like that request was not transformed by v-p-s. I am still at a loss why this would...

does the same happen if you use vue? or vanilla vite? `npm create vite@latest`

Is this inside a container or are you using a network fs? Did you edit the paths in your report in any way? no username in /home confuses me a...

there is https://github.com/vitejs/vite/issues/16481 but thats more about a possible root relative path confusion, you don't happen to have `/custom` elsewhere?

is this still occuring? as mentioned above i was unable to reproduce on manjaro and without a reproduction its really hard to work on a fix.

thank you too

I'm on the fence about this. If file options take precedence, then users can no longer override them via env, which makes env less useful. Esp if someone checked in...