Dominik G.

see #341 #1024

.svelte files never end up in the browser cache. do you mean js modules compiled from .svelte files? please file a separate issue with a reproduction for this.

moving to svelte repo [svelte5 repl](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAAyWMQQrDIBQFr_J5dNGC0L2NgZ6jdiHJTxGMiv4Einj3Il3ODEzD5gNX6FdDdDtD45kzFOSbB9STgzAUajrKMsxUl-KzUHDxYyykWsw2Wgks1FYnrpOhSy4p1-vtMcpY0ShkqHUbp_t_MdsIhT2tfvO8Qks5uL_7D-Pm_OeTAAAA)

adding info from @gtm-nayan cause is in acorn-typescript that just has one scope for both https://github.com/TyrealHu/acorn-typescript/blob/8956dc50370c7ee2ea97a3c903611079192b28d5/src/index.ts#L2720 https://github.com/acornjs/acorn/blob/12ad1164a70dbe804f1ece822f34d100545f1afa/acorn/src/lval.js#L267

+1 to remove the import (possibly needs an eslint disable rule comment to prevent it from adding it back) however this could break deno compatibility for users that use svelte...

`'Deno' in window` ?!!! that reads off. surely there is no `window` global on deno serverside? ``` const cwd_parent=typeof process !== 'undefined' ? process : (typeof Deno !== undefined ?...

to give users a chance to shim process.cwd if we don't want to do this, we'd have call `get_cwd` during compile instead of eagerly determining it on module load.

allowing the svelte compiler to emit ts that then has to be postprocessed is going to create a lot of effort. even if it works in vite, what about all...

OT: that was actually Ben and the other way around. Inside v-p-s generate a separate vite plugin for each preprocessor so that you can see the transformations in vite-plugin-inspect. But...

vite has library-mode too but thats not a focus. svelte-package is indeed one of the cases we'd have to look into, good call.