Runtime error on a page kills `wasp start` when prerendering is set

Wasp: 0.25.0

To reproduce you can:

• Create a minimal project.
• Put something like throw new Error("gmali"); at the top of main page.
• Run wasp start and load the page. You'll see the error in the Chrome console.
• Then configure the page with { prerendering: true }, reload and see wasp start die.

Is this expected behavior for frameworks that do prerendering? Do others keep the dev server running?