You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// On apps with Prerendering enabled, to have the best experience for the end user un-comment one of the following lines:
35
-
// self.prerenderMode = 'always'; // Demo: https://sales.bitplatform.dev/ (Always show pre-render without offline support)
36
-
// self.prerenderMode = 'initial'; // Demo: https://todo.bitplatform.dev/ (Pre-Render on first site visit + Offline support)
37
+
self.mode='NoPrerender';// Modern PWA app that **starts immediately** and lazy-loads assets as needed.
38
+
// If network connectivity is lost and the user navigates to a new page requiring lazy-loaded JS/WASM/image files, the app might break.
39
+
// Recommended if the app uses PWA for benefits other than offline support, such as installability, push notifications, etc.
40
+
// Demo: https://adminpanel.bitplatform.dev/
41
+
42
+
// self.mode = 'InitialPrerender'; // If pre-rendering is enabled in the `Server.Web` configuration, this mode fetches the site's document only on the first load of the app.
43
+
// Useful for SEO-friendly apps, and to display content on the initial visit while files download. Subsequent visits avoid server pressure from pre-rendering.
44
+
// Demo: https://todo.bitplatform.dev/
45
+
46
+
// self.mode = 'AlwaysPrerender'; // If pre-rendering is enabled in the Server.Web configuration, this mode fetches the site's document on every load of the app.
47
+
// The reason behind fetching the document on every app load is that Blazor WebAssembly's runtime might takes some time to kick in on low-end mobile devices,
48
+
// so if the user refreshes the page or visits a new page, it shows the pre-rendered document while the Blazor WebAssembly runtime is loading.
49
+
// Downside: Increases server load due to frequent pre-rendering.
0 commit comments