Packages

Application projects reference the FSharp.CloudEdge libraries by NuGet package ID and version. The release version is 0.1.0. Each ID matches its assembly name; the package catalog lists the 47 selected packages and their versioned NuGet URLs.

Release availability

All 47 packages in the 0.1.0 release are published on nuget.org. Browse all FSharp.CloudEdge packages on NuGet, or use the package catalog to find a specific library.

The release uses the published Xantham.Fable.Core and Xantham.Fable.Core.TS 0.1.0 packages. Application projects restore these dependencies through NuGet; contributors can use the source build when regenerating or changing the bindings.

Add the package your application uses

For a Worker:

dotnet add package FSharp.CloudEdge.Runtime.Workers --version '0.1.*'

For a .NET program that manages Workers:

dotnet add package FSharp.CloudEdge.Management.Compute --version '0.1.*'

The latter brings in FSharp.CloudEdge.Core.Api transitively. You can list it explicitly when your project uses its types. First Worker and First Deploy show complete project files.

Samples use 0.1.* to accept stable patches in the 0.1 series without moving to 0.2. Catalog links identify the concrete 0.1.0 release. For repeatable application builds, commit a NuGet lock file and use locked restore in CI; deliberately refresh it when adopting a patch. Release validation pins the candidate and support versions exactly and records every resolved package.

The NuGet feed is https://api.nuget.org/v3/index.json. A package page such as https://www.nuget.org/packages/FSharp.CloudEdge.Runtime.Workers/0.1.0 is for browsing; it is not a package source URL.

Fable and npm dependencies

CloudEdge's runtime and Fable support packages contain their F# source as well as .NET assemblies. Fable uses that source when compiling the application to JavaScript. NuGet restores the published Xantham support dependencies transitively. Release validation compiles the site's actual examples against this package combination. Application developers do not run the binding generators.

NuGet does not install the upstream JavaScript SDKs. Where an example imports an npm SDK, install the exact package version shown on its library page. Worker-native APIs such as Request, D1, and R2 are supplied by the Workers runtime. The platform type declarations describe those APIs; they are not a JavaScript runtime implementation to bundle.

Verify a candidate before publication

Maintainers can build the selected packages from the repository's checked-in source:

dotnet run --project tools/NuGetRelease -- pack
dotnet run --project tools/NuGetRelease -- examples --fable

Packing writes artifacts/nuget-release/0.1.0/packages and a dependency-ordered manifest with package hashes. The consumer checks use that feed for CloudEdge and nuget.org for external dependencies, with an isolated cache. This is package consumption testing before any public upload.

After publication, run the same consumers against nuget.org alone:

dotnet run --project tools/NuGetRelease -- availability
dotnet run --project tools/NuGetRelease -- examples --fable --public

The maintainer release guide covers ownership, release checks, and publication. Package validation is distinct from hosted runtime verification.