Rom

> While Vike does support custom error pages—which is a nice feature—during development, developers typically expect that once they fix a bug, the page will automatically recover and render normally...

Yea, I was actually thinking this morning that runtime errors (not syntax errors) aren't shown in error overlays. I'll have a look at this.

Vite doesn't support that yet, alhtough it's on the team's radar. - https://github.com/vitejs/vite/issues/2076 - https://github.com/vitejs/vite/pull/20526#issuecomment-3166299993

I could reproduce with a simple app (that doesn't use `@cloudflare/vite-plugin`). I've updated the bug report.

I see, makes sense. One weird thing is that removing the `@brillout/picocolors` import from Telefunc's `utils/assert.ts` (which is loaded on both client- and server-side) fixes the issues (https://github.com/brillout/telefunc/commit/d9967bd1541d6f6eef7ffdf793ce9bff5e4a16c3) while importing...

CC @magne4000

> I think the error page can be enhanced for better UX with display which part of code cause the errors and button for retry I agree, in development, it...

> like nextjs Neat, I like that Next.js shows the first error message first. Although I think it should show all errors without forcing the user to use pagination.

It's still very much a consideration to make Vike use Vite's error modal. What I'm trying to understand is how much of a DX improvement it would be. For me...

> When the "Internal Server Error" screen appears, the live reload feature no longer works [...] Can this be prioritized Discussion resumed over there: - https://github.com/vikejs/vike/issues/2511