TS enums no longer get transpiled as expected starting with `vite-plugin-svelte@4.0.0-next.0` in `*.svelte` files

[ndom91]

Describe the bug

We have a component which uses an enum as a value in a .svelte file. When using @sveltejs/vite-plugin-svelte@3.1.1 the following works as expected. However, when upgrading to @sveltejs/vite-plugin-svelte@4.0.0-next.0, we begin seeing errors about ReferenceError: Can't find variable: Action

<script lang="ts">
	enum Action {
		Create = 'createPr',
		CreateDraft = 'createDraftPr'
	}

	const actions = Object.values(Action);
	const labels = {
		[Action.Create]: 'Create PR',
		[Action.CreateDraft]: 'Create Draft PR'
	};
  ...

In 3.1.1 the code above produced compiled output like this:

var Action = /* @__PURE__ */
((Action2) => {
    Action2["Create"] = "createPr";
    Action2["CreateDraft"] = "createDraftPr";
    return Action2;
})(Action || {});

Whereas in 4.0.0-next.0 that output is missing entirely. This seems to only be effecting enums in .svelte files. Enums used like this in .ts files are unaffected.

Reproduction URL

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA1WQwWrDMAyGX8WIQVoWuu2aNoWy3Rd6rXtwPWV4c-Rgy4UR8u7Ddrt2B2NL-iV9_ifojcUAzWECUgNCA7txhBr4Z0xBOKNlhBqCi16nzCZob0YWVtFnK4GDhK0kyUhxEDvNxpGYUkLyq0fFKFpR6fzqfFXfV9686vlWzmHnqySZJaVLOwosVJ4aRCveT1-oeXVWNmJYlG3L9U1p1QltEl4IDkWyKvuOjaguTN3-ivJfkhnudAWx2xeovCkdiyy0i5ToHwIrxsVz5iDJfaTigiHtcUDixfLKU3oeW_Gyvvxy81T8TB7S5hSZHQlH2hr93U5_I-bscc6GRkx5Tu4uHVuoYXAfpjf4AQ37iPNx_gWxO40x3AEAAA==

Reproduction

In the above svelte-5 playground URL, you can see that the enum Action also results in the error "Action is not defined".

This link leads to a PR of our project where I bumped the dependencies and moved the enum Action down from the <script lang="ts" context="module"> to the normal <script /> tag because the enum was no longer being imported from anywhere and it's simpler that way. The PR also includes bumping a few Svelte related packages, except the vite-plugin-svelte, because that was giving us troubles.

Logs

No response

System Info

System:
  OS: Linux 6.10 NixOS 24.05 (Uakari) 24.05 (Uakari)
  CPU: (14) x64 Intel(R) Core(TM) Ultra 7 155U
  Memory: 16.20 GB / 30.87 GB
  Container: Yes
  Shell: 5.2.26 - /run/current-system/sw/bin/bash
Binaries:
  Node: 20.14.0 - /nix/store/ilkfhnqz4xczrliqjva8770x2svbfznd-nodejs-20.14.0/bin/node
  npm: 10.7.0 - /nix/store/ilkfhnqz4xczrliqjva8770x2svbfznd-nodejs-20.14.0/bin/npm
  pnpm: 9.5.0 - /nix/store/zw38hg36phakmnk3lxglyzvjwf2pivsa-corepack-nodejs-20.14.0/bin/pnpm
  bun: 1.1.20 - /run/current-system/sw/bin/bun
Browsers:
  Chromium: 127.0.6533.88

[dominikg]

svelte5 understands ts syntax in .svelte files without needing a preprocessor, however it does not work with typescript features that have code output. for that to work you have to change vitePreprocess() to vitePreprocess({script: true}) in svelte.config.js

[ndom91]

Ah okay, I'm curious why that's the default? 🤔

But thanks for the quick response!

[dominikg]

Ah okay, I'm curious why that's the default? 🤔

But thanks for the quick response!

we might reevaluate that default. in general i think most users/components don't need this feature so it would save processing time. But it is kind of opaque and the current feedback isn't great as you already experienced.

Would you be less concerned about this default if a message told you about it?

[ndom91]

Yeah maybe svelte-check could warn if enum's or similar are used in .svelte files 🤔 It'd definitely save folks some headache tryign to figure out what's going on

[frederikhors]

@dominikg this should be handled with an error at compile time or it will errors on runtime only as in my case.

Plus, I think the default should be changed to handle this by default if I use Typescript.

[frederikhors]

Can you please re-open this, @ndom91?

[ndom91]

Can you please re-open this, @ndom91?

Sure, happy to discuss

[dominikg]

forcing an extra unneeded transpile on all users just because some users use enums or other code generating features of typescript in some files is not great.

Ideally we find a way to avoid this scenario. For the record the breaking changes of 4.0 do mention that scripts are no longer preprocessed for typescript by default

disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#892)

So this might also just be something that needs better communication / warnings.

There's also the question of how useful enums in .svelte script blocks are. Another way of avoiding this problem is putting them in .ts files and import.

[frederikhors]

This is not an issue with enums only, with the below code:

<script lang="ts">
    // ...

    $effect(() => {
        // ...

        if (input) {
            input.value = someOne || someTwo;
        }
    });
</script>

I get:

Unexpected token

If you expect this syntax to work, here are some suggestions: 
If you use typescript with `svelte-preprocess`, did you add `lang="ts"` to your `script` tag? 
Did you setup a `svelte.config.js`? 
See https://github.com/sveltejs/language-tools/tree/master/docs#using-with-preprocessors for more info.svelte(js_parse_error)

with someTwo highlighted in red in my IDE.

Or this other code:

<script lang="ts">
    const options: Partial<BaseOptions> = {
        // ...
        onReady() {
            //...
        } // <-- here the red error
    };
</script>

the error:

Unexpected token `}`. Did you mean `}` or `{"}"}`?

If you expect this syntax to work, here are some suggestions: 
If you use typescript with `svelte-preprocess`, did you add `lang="ts"` to your `script` tag? 
Did you setup a `svelte.config.js`? 
See https://github.com/sveltejs/language-tools/tree/master/docs#using-with-preprocessors for more info.svelte(js_parse_error)

So now I think we should decide if Svelte 5 can handle typescript or not alone or am I wrong?

[frederikhors]

So I think the second sentence here is false:

[smart]

Just upgraded to 4 and ran into this issue. Took a while to debug with the error messages only being something like expected "{" but got ";", I think the issue was I didn't even know it was enum related until digging deep into the codebase. enabled script: true and it works fine.