Open Issues Need Help
View All on GitHubEasily call Services in separate threads with WebWorkers and SharedWebWorkers. Run Blazor WASM in the ServiceWorker.
Easily call Services in separate threads with WebWorkers and SharedWebWorkers. Run Blazor WASM in the ServiceWorker.
Easily call Services in separate threads with WebWorkers and SharedWebWorkers. Run Blazor WASM in the ServiceWorker.
Easily call Services in separate threads with WebWorkers and SharedWebWorkers. Run Blazor WASM in the ServiceWorker.
AI Summary: The issue is a `ReferenceError: Range is not defined` occurring during Blazor WASM app startup, specifically impacting the FluentUI library used in the application. The error originates from `spawndev.blazorjs.webworkers.faux-env.js`, suggesting a conflict between the SpawnDev.BlazorJS.WebWorkers library and FluentUI's reliance on the `Range` object, which might not be available in the WebWorker context. The task involves debugging this conflict, potentially by investigating FluentUI's compatibility with WebWorkers, ensuring necessary polyfills are included, or adjusting the library's initialization to avoid the `Range` object in the WebWorker environment. Adding `webworker-enabled` to relevant scripts might not be sufficient if the problem lies within FluentUI's internal dependencies.
Easily call Services in separate threads with WebWorkers and SharedWebWorkers. Run Blazor WASM in the ServiceWorker.