Suave 3.7.2
dotnet add package Suave --version 3.7.2
NuGet\Install-Package Suave -Version 3.7.2
<PackageReference Include="Suave" Version="3.7.2" />
<PackageVersion Include="Suave" Version="3.7.2" />
<PackageReference Include="Suave" />
paket add Suave --version 3.7.2
#r "nuget: Suave, 3.7.2"
#:package Suave@3.7.2
#addin nuget:?package=Suave&version=3.7.2
#tool nuget:?package=Suave&version=3.7.2
Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
| 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
- FSharp.Core (>= 10.0.102)
NuGet packages (64)
Showing the top 5 NuGet packages that depend on Suave:
| Package | Downloads |
|---|---|
|
Aardvark.Service
Aardvark is an open-source platform for visual computing, real-time graphics and visualization. |
|
|
FsLab
FsLab is a combination package that supports doing data science with F#. FsLab includes literate scripting converted to HTML and PDF, and by default references Deedle (a data frame library), FSharp.Data (for data access) and XPlot (for visualization). You can optionally add any other nuget packages. |
|
|
Suave.DotLiquid
Suave.DotLiquid provides Liquid templates for Suave web server. |
|
|
SuaveServerWrapper
A wrapper for suave.io APIs to call from C# |
|
|
Logary.Services.SuaveReporter
Logary is a high performance, multi-target logging, metric and health-check library for mono and .Net. |
GitHub repositories (2)
Showing the top 2 popular GitHub repositories that depend on Suave:
| Repository | Stars |
|---|---|
|
msarilar/EDEngineer
An overlay to track Elite Dangerous blueprints progress in real time
|
|
|
rogeralsing/Microphone
|
| Version | Downloads | Last Updated |
|---|---|---|
| 3.7.2 | 89 | 10/15/2026 |
| 3.7.1 | 44 | 10/15/2026 |
| 3.7.0 | 46 | 10/15/2026 |
| 3.6.1 | 767 | 10/7/2026 |
| 3.6.0 | 148 | 10/5/2026 |
| 3.5.0 | 849 | 9/9/2026 |
| 3.4.6 | 6,720 | 8/29/2026 |
| 3.4.5 | 193 | 8/26/2026 |
| 3.4.4 | 3,449 | 7/13/2026 |
| 3.4.3 | 10,905 | 6/1/2026 |
| 3.4.2 | 586 | 5/31/2026 |
| 3.4.1 | 279 | 5/30/2026 |
| 3.4.0 | 512 | 5/18/2026 |
| 3.4.0-beta | 149 | 5/14/2026 |
| 3.3.1 | 398 | 5/11/2026 |
| 3.3.1-beta3 | 143 | 5/6/2026 |
| 3.3.1-beta2 | 137 | 5/5/2026 |
| 3.3.1-beta1 | 129 | 5/5/2026 |
| 3.3.1-beta | 139 | 5/4/2026 |
| 3.3.0 | 372 | 5/2/2026 |
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`