Use empty export list instead of unused export

[MattiasBuelens]

This way the file is still parsed as a module, even though it doesn't import or export anything. 😉

[jakearchibald]

Nice. I was staying away from things that were 'meaningful' to JavaScript, but seems like this is removed from the output too.

[MattiasBuelens]

It's... interesting. The input is a module, but the output could be parsed as a module or as a script. You might expect TypeScript to add export {} to the output to ensure it's unambiguously a module, see microsoft/TypeScript#28890. If that happened, then our workaround would turn our output into a module which means we would have to load it differently, e.g. with new Worker("...", { type: "module" }).

Let's hope TypeScript fixes the worker types first, so we can get rid of this workaround altogether. 😅

[jakearchibald]

If it happens the other way around, I guess exporting a type will still work.

[MattiasBuelens]

I don't know. If a file contains only type exports, can that only be used as a module? Or should it also be usable as a script? 🤷‍♂