Suave.DotLiquid
3.7.2
dotnet add package Suave.DotLiquid --version 3.7.2
NuGet\Install-Package Suave.DotLiquid -Version 3.7.2
<PackageReference Include="Suave.DotLiquid" Version="3.7.2" />
<PackageVersion Include="Suave.DotLiquid" Version="3.7.2" />
<PackageReference Include="Suave.DotLiquid" />
paket add Suave.DotLiquid --version 3.7.2
#r "nuget: Suave.DotLiquid, 3.7.2"
#:package Suave.DotLiquid@3.7.2
#addin nuget:?package=Suave.DotLiquid&version=3.7.2
#tool nuget:?package=Suave.DotLiquid&version=3.7.2
Suave.DotLiquid provides Liquid templates for Suave web server.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. 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. |
-
net10.0
- DotLiquid (>= 2.3.197)
- FSharp.Core (>= 10.0.102)
- Suave (>= 3.2.0 && < 4.0.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 |
|---|---|---|
| 3.7.2 | 35 | 10/15/2026 |
| 3.7.1 | 35 | 10/15/2026 |
| 3.7.0 | 35 | 10/15/2026 |
| 3.6.1 | 95 | 10/7/2026 |
| 3.6.0 | 88 | 10/5/2026 |
| 3.5.0 | 134 | 9/9/2026 |
| 3.4.6 | 115 | 8/29/2026 |
| 3.4.5 | 120 | 8/26/2026 |
| 3.4.4 | 163 | 7/13/2026 |
| 3.2.2 | 1,023 | 1/16/2026 |
| 3.2.1 | 1,095 | 1/10/2026 |
| 2.7.0-beta1 | 287 | 7/3/2023 |
| 2.7.0-beta | 297 | 3/3/2023 |
| 2.6.2 | 3,419 | 1/26/2022 |
| 2.6.1 | 2,326 | 5/15/2021 |
| 2.6.0 | 6,034 | 12/8/2020 |
| 2.6.0-beta | 678 | 7/18/2020 |
| 2.5.6 | 5,354 | 9/7/2019 |
| 2.5.5 | 3,355 | 6/5/2019 |
| 2.5.4 | 3,654 | 4/14/2019 |
Behaviour change:** a binding that cannot be bound (e.g. its port is already in use) is now reported to the caller. `startWebServer` throws the `SocketException` instead of returning normally, so a `startWebServer cfg app; 0` program exits with a non-zero code and supervisors (systemd `Restart=on-failure`, Docker restart policies) see the failure. With `startWebServerAsync`, `listening` raises the exception instead of never completing (a program blocked on it hung for ever, even on SIGTERM) and the server task is faulted with it. With several bindings, one that fails stops the ones that did start, so `startWebServer` throws instead of carrying on with only some of them. Stopping the server by cancelling its token still completes cleanly. Adds `AsyncResultCell.fail`