Poenaru Mihai

> Renaming it to `.js` solves the issue. Just commenting to let other people know that this also solved the issue for me. I have no idea why. I'm also...

I have the same issue. Not a dealbreaker since I can still run everything just fine without '--bun' but it really should be fixed. It essentially kneecaps sveltekit.

@Jarred-Sumner Depending on the prio of this issue, maybe specify in the docs to avoid using `--bun` until this is fixed? It could cause a lot of headaches for a...

@Bewinxed for me it just worked to not use `--bun`, so just do `bun run your_script`. Of course you can't use all the cool bun apis if you do that....

@Jarred-Sumner Maybe I'm not doing it right, but it still doesn't work for me. Here is my minimal +page.server.ts reproducer(same one as in my duplicate issue #9846) ```ts import type...

Small update, making a basic project with bun init and then bun run on the same conde (minus the svelte load, of course) works: normal fetch ```js { headers: {...

After trying various things, what worked is using `bun run dev` instead of `bun --bun run dev`. Not sure if this is a performance hit or not. I'm not sure...

As long as the prod version works without issue (and it does) I'm not too attached with vite dev being on node for the time being, however this definitely should...

Ok tested on Mac as well: VITE v5.2.8 ready in 314 ms ➜ Local: http://localhost:5173/ ➜ Network: use --host to expose ➜ press h + enter to show help normal...

Closing this in favor of #4718 I don't know how I didn't stumble upon it sooner but no point in having this be a duplicate issue. I'll comment on there.