UnoCSS with SvelteScoped not working in Vite dev mode

[FireSpike0]

I've created a simple project using SvelteKit with the official SvelteKit Npm template. After that I've configured SvelteScoped according to the official documentation. When starting Vites dev mode with npm run dev the page initially loads and all styles are working. But if I edit the default routes HTML (e.g. appending or removing a single character within a paragraph) and reload the page (regardless of automatic or manual reload), the styles of the page break in most cases. "Break" in this context means, that UnoCSS styles will flash up for short time and then disappear. After some investigation I found out, that the styles in the head section always contain HTML instead of CSS, if the bug occurs:

The style node if the styles work:

<style type="text/css" data-vite-dev-id="/Projects/feedback/src/routes/+page.svelte?svelte&amp;type=style&amp;lang.css">._color-red_van38g{--un-text-opacity:1;color:rgb(248 113 113 / var(--un-text-opacity))}._underline_van38g{text-decoration-line:underline}.s-y_bCXRrkrYfP{}</style>

The style node if the styles breaked:

<style type="text/css" data-vite-dev-id="/Projects/feedback/src/routes/+page.svelte?svelte&amp;type=style&amp;lang.css"><h1 class="color-red underline">Hello, world!</h1>
<p>Hello, world!</p>
</style>

The HTML contained in the style node corresponds exactly to the HTML contained in my default route.

What I've found out is, that the flashing of the styles results from another style node, which is always removed when loading the page: It gets removed by the client.js file of SvelteKit because this node is a style node with the data-sveltekit attribute.

<style data-sveltekit="">._color-red_van38g{--un-text-opacity:1;color:rgb(248 113 113 / var(--un-text-opacity))}._underline_van38g{text-decoration-line:underline}.s-y_bCXRrkrYfP{}</style>

Does anyone have an idea, what's going on here? Any help (or a hint, that this sounds more like a Vite / SvelteKit problem) would be very appreciated.

EDIT: I've pushed the repositry with my configuration files to https://github.com/FireSpike0/feedback

[FireSpike0]

After further investigation I can reproduce it with the sveltekit-scoped example from the UnoCSS repository: It seems that if the compilerOptions.moduleResolution from the tsconfig.json is set to bundler, the problem shows up. This option is the default if the project was created using the suggested command by Svelte npm init svelte. If I remove the option, I cannot reproduce the bug anymore (but because the bug shows up randomly after some reloads, I'm not entirely sure).

EDIT: In my repository I still can reproduce the issue, regardless of whether the option mentioned above is set or not.