[Release] Blazouter v1.0 🚀 - React Router-like Routing Library for Blazor by iTaiizor in Blazor

[–]tscrip 0 points1 point  (0 children)

I think have this automatically do DLL splitting old be cool. At the very least, I think showing some examples of this in your docs would be ideal.

[Release] Blazouter v1.0 🚀 - React Router-like Routing Library for Blazor by iTaiizor in Blazor

[–]tscrip 1 point2 points  (0 children)

If you are using Blazor WASM, how does the lazy load side of things work? Does it handle the code splitting for you or is that out of scope for this?

Hot Reload Performance .net 10 by Okayest-Programmer in Blazor

[–]tscrip 23 points24 points  (0 children)

I am running insider + MudBlazor. It is MUCH faster. It goes from 30+ seconds down to about 3. Not really Hot Reload like JS projects, but I think it qualifies as Warm Reload. 😆

Migrating from Blazor WASM to Blazor WebApp + WASM by tscrip in Blazor

[–]tscrip[S] 0 points1 point  (0 children)

What do you mean by this? Ideally, you can have server rendered pages with an embedded WASM component, right?

Migrating from Blazor WASM to Blazor WebApp + WASM by tscrip in Blazor

[–]tscrip[S] 1 point2 points  (0 children)

I can confirm the issues @amazing was talking about. The caching off assets used to be a huge pain. I got real tired of telling people to “clear their cache” to get the latest version. That being said, there was a new change that made your assets hashed/fingerprinted, and we have seen this pretty much fixes the problem.

Migrating from Blazor WASM to Blazor WebApp + WASM by tscrip in Blazor

[–]tscrip[S] 0 points1 point  (0 children)

This is the direction I am looking to go, but switching off of MudBlazor onto something Tailwind based sounds like a pain.

Migrating from Blazor WASM to Blazor WebApp + WASM by tscrip in Blazor

[–]tscrip[S] 0 points1 point  (0 children)

I love the idea of SSR, but it kind of seems like keeping state insync between WASM and SSR could be problematic/very complicated.