Vite cannot parse error messages thrown during SSR

[jansedlon]

What version of Bun is running?

1.2.4+fd9a5ea66

What platform is your computer?

Darwin 24.3.0 arm64 arm

What steps can reproduce the bug?

I'm not really sure. I think that making a react router application and then intentionally writing invalid code to throw an error should do it.

What is the expected behavior?

I should be able to see the error that was thrown was anytime this happens, i just see

Internal server error: undefined is not an object (evaluating 'varName.trim').

What do you see instead?

It doesn't matter if the error originates from drizzle-orm or something on the frontend.

It always happens in function called ssrRewriteStacktrace which is implemented by vite.

In this particular example if I run it with Node, you can see that i was trying to call a function that was not defined.

Additional information

I have been seeing this issue for many months now and it's kind of a blocker for me. Seeing issues like this are the reason why i'm hesitant to migrate to bun.

It makes it really hard to develop something in Bun if i cannot debug what happened 😄

[DimitryDushkin]

Same here

[DonIsaac]

We format stack traces slightly differently from node. This appears to happen in Vite's stack trace parsing logic; even better, it looks like they've fixed it. I'll close this in a few days after the next Vite release unless someone confirms this is still a problem (post release)