Add WebAssembly-specific scheduler and update browserwasm condition (#268)

Use WasmScheduler.Default for WebAssembly targets to handle lack of multithreading, and update the csproj condition for browserwasm to use EndsWith for better compatibility.

Author: ChrisPulman

src/ReactiveUI.Uno/Builder/UnoReactiveUIBuilderExtensions.cs

@@ -72,7 +72,12 @@ public static IReactiveUIBuilder WithUno(this IReactiveUIBuilder builder)
 
         return builder
             .WithUnoScheduler()
+#if __WASM__ || BROWSERWASM
+            // WebAssembly doesn't support multithreading, use WasmScheduler instead of TaskPoolScheduler
+            .WithTaskPoolScheduler(WasmScheduler.Default)
+#else
             .WithTaskPoolScheduler(TaskPoolScheduler.Default)
+#endif
             .WithPlatformModule<Uno.Registrations>()
             .WithUnoDictionary();
     }

src/ReactiveUI.Uno/ReactiveUI.Uno.csproj

@@ -29,7 +29,7 @@
   <ItemGroup>
     <PackageReference Include="ReactiveUI" />
   </ItemGroup>
-  <ItemGroup Condition="'$(TargetFramework)' == 'net9.0-browserwasm'">
+  <ItemGroup Condition="$(TargetFramework.EndsWith('0-browserwasm'))">
     <PackageReference Include="Reactive.Wasm" />
   </ItemGroup>
   <ItemGroup>