Dominik G.

thought about some open tickets in this repo today and this one is still strange. you can easily override even a default env (if you set one, opting in to...

in the interim, you might be able to use svelte-preprocess instead, that uses typescript under the hood.

The reasoning for using target esnext was that the resulting js output is going through vite anyways, so any downleveling would happen there. But obviously this only covers js features,...

your reproduction does not contain use of $props and you did not share your fork, so we can't tell whats going on.

with the upcoming support of rolldown-vite in vite-plugin-svelte you can use transformWithOxc via vitePreprocess that takes the values from your `tsconfig.json` so you should be able to set target lower....

there is an upcoming PR in svelte that also enables `using` in svelte script, however it might not work as you expect. see this PR where the clock isn't bound...

i'm going to close the issue here as the example provided makes an assumption on how using works inside svelte components that isn't even specced and vite-plugin-svelte can't do anything...

please contribute in the svelte repo on how you want to use `using` in svelte components

@ryanylee in a separate issue with a link to a minimal reproduction. Please make sure to mention rolldown-vite and the exact versions you use.

The issue here is that vite plugin svelte runs preprocess and compile within the same transform so other plugins cannot get the preprocessed output to further change that before compile....