No wasm mode

[maxence-charriere]

Summary

• Possibility to see pre-rendered page by adding the URL query ?wasm=false
• Prerendered content is now at the same dom depth as the wasm rendered one

[maxence-charriere]

@oderwat after using pre-rendering for a while, I doubt the value of having the PreRenderer interface. I feel like just using the mount/nav flow on the server side would be the same.

Removing it might also simplify the code base and if something specific is done on the server side, we can still use if app.IsServer {}.

Do you use the PreRenderer? Any opinion about it?

[oderwat]

We do not use PreRender() right now. I wonder about the implications. I do not want to have Render() / OnMount() ever being called on the server because this would need changes to the code (to gate it everywhere "when on the server"), does it? For me and my idea about the PWA, there is no real valid HTML that I can create in the server. Maybe I did misunderstand you, though?

I would prefer a strict separation of what is rendered for and send to the browser and was is rendered in the client.

Perhaps my idea about this is wrong, but an SPA (PWA) just says, "there would be an app here if you had JavaScript activated, so long look at this information that is just not what it would be if you used the app" ;-)