Aardworx.WebAssembly.Dom
1.2.5
See the version list below for details.
dotnet add package Aardworx.WebAssembly.Dom --version 1.2.5
NuGet\Install-Package Aardworx.WebAssembly.Dom -Version 1.2.5
<PackageReference Include="Aardworx.WebAssembly.Dom" Version="1.2.5" />
<PackageVersion Include="Aardworx.WebAssembly.Dom" Version="1.2.5" />
<PackageReference Include="Aardworx.WebAssembly.Dom" />
paket add Aardworx.WebAssembly.Dom --version 1.2.5
#r "nuget: Aardworx.WebAssembly.Dom, 1.2.5"
#:package Aardworx.WebAssembly.Dom@1.2.5
#addin nuget:?package=Aardworx.WebAssembly.Dom&version=1.2.5
#tool nuget:?package=Aardworx.WebAssembly.Dom&version=1.2.5
WebAssembly libraries for Aardvark
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
- Aardvark.Application (>= 5.6.4 && < 5.7.0)
- Aardvark.Base (>= 5.3.21 && < 5.4.0)
- Aardvark.Base.FSharp (>= 5.3.21 && < 5.4.0)
- Aardvark.Dom.Elm (>= 1.1.0 && < 1.2.0)
- Aardvark.Dom.Remote (>= 1.1.0 && < 1.2.0)
- Aardworx.Rendering.WebGL (= 1.2.5)
- Aardworx.WebAssembly (= 1.2.5)
- FSharp.Core (>= 8.0.300)
- FSharp.Data.Adaptive (>= 1.2.26 && < 1.3.0)
- Microsoft.AspNetCore.Components.WebAssembly (>= 8.0.26 && < 8.1.0)
- Microsoft.AspNetCore.Components.WebAssembly.DevServer (>= 8.0.26 && < 8.1.0)
- Silk.NET.OpenGLES (>= 2.15.0 && < 2.16.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.2.8 | 80 | 5/20/2026 |
| 1.2.7 | 103 | 5/18/2026 |
| 1.2.6 | 102 | 4/28/2026 |
| 1.2.5 | 101 | 4/26/2026 |
| 1.2.4 | 94 | 4/26/2026 |
| 1.2.3 | 96 | 4/26/2026 |
| 1.2.2 | 107 | 4/26/2026 |
| 1.2.1 | 93 | 4/25/2026 |
| 1.2.0 | 93 | 4/25/2026 |
| 1.1.14 | 312 | 11/6/2025 |
| 1.1.13 | 239 | 10/22/2025 |
| 1.1.12 | 248 | 10/16/2025 |
| 1.1.11 | 247 | 2/22/2025 |
| 1.1.10 | 225 | 10/21/2024 |
| 1.1.9 | 282 | 10/19/2024 |
| 1.1.8 | 222 | 10/1/2024 |
| 1.1.7 | 252 | 5/13/2024 |
| 1.1.6 | 265 | 9/27/2023 |
| 1.1.5 | 249 | 9/27/2023 |
| 1.1.4 | 233 | 9/25/2023 |
fix: shader-output type for the `"Normals"` framebuffer attachment was hardcoded to `V3d`, regardless of the actual texture format. Every other attachment derives its type from `TextureFormat.toShaderType`, but `Normals` was special-cased — so a fragment writing `[<Normal>] : V3f` to an `Rgba32f` G-buffer died with `[FShade] cannot convert Normals value from V3f to V3d` (FShade has no V3f→V3d converter). Removed the special case in both `shaderType` helpers (`AssembleModule` / `CreateProgram` paths). `Normals` now uses the texture format like everything else, and FShade's built-in V3f→V4f widening (appending `1.0f`) handles the typical `Rgba32f` G-buffer naturally.