Ranvier.View

Template components, server rendering, hydration, DOM bindings, motion parts and build-time analyzers for Ranvier, on .NET and Fable.

Repository · Documentation

Ranvier.View is the view layer of the Ranvier family:

• Ranvier (docs): the reactive core, Ranvier.Elmish, Ranvier.Query, Ranvier.Wire and Ranvier.CSharp.
• Ranvier.Css (docs): typed CSS, generated bindings, static extraction and Ranvier.Css.View.
• Ranvier.Persistence: persisted signals and store adapters.

The view projects, experiments, examples and checks were copied from the Ranvier repository. The core and CSS packages are pinned NuGet dependencies, so this repository builds on its own; a sibling checkout is supported for coordinated development.

Packages

Package	Contents
Ranvier.View	Typed templates, view sugar, keyed lists, arms, boundaries and server HTML rendering.
Ranvier.View.Dom	The browser renderer: mounting, hydration of server HTML, delegated events and generated HTML bindings.
Ranvier.View.Anime	Motion parts for templates over anime.js, omitted by the server renderer.
Fable.Ranvier.Anime	Typed anime.js bindings for Fable with Ranvier integration.
Ranvier.Analyzers	F# analyzers that report Ranvier traps at build time.

The four libraries share a version and depend on each other at exactly it. Each also packs as a .Traced package over the traced core packages, and carries its F# sources under fable/ for Fable consumers.

Layout

• src/: the four libraries and Fable.Ranvier, the unpacked Fable DOM helper the experiments use.
• experiments/: Ranvier.View.Arms (Arms.Match and its Fable plugin), the representation checks, the DOM twin and the view testing API.
• tests/Ranvier.View.Twin.Tests, fable/: the twin conformance suite and the Fable suites of the anime packages.
• examples/: the Fable playground, the Motion pages and the server hydration example.
• tools/: the DOM binding generator and the analyzers with their tests and truth fixtures.
• docs/: the Nacara site (Views, Server, Analyzers and the browser examples) and its compiled samples.

Setup and checks

Install .NET 10, the .NET 8 runtime and Node.js 26 or later. All workflows run through Partas.Build:

rtk dotnet fsi build.fsx -- tools
rtk dotnet fsi build.fsx -- test

test builds the solution and runs every group. CI runs each group as a shard:

rtk dotnet fsi build.fsx -- test --group view       # representation checks, docs samples, playground, twin
rtk dotnet fsi build.fsx -- test --group sugar      # DOM generator output, README samples, generated types
rtk dotnet fsi build.fsx -- test --group anime      # Fable.Ranvier.Anime under jsdom and Chromium
rtk dotnet fsi build.fsx -- test --group motion     # Motion parts and the Motion example pages
rtk dotnet fsi build.fsx -- test --group hydration  # server hydration example and alternative backends
rtk dotnet fsi build.fsx -- test --group arms       # Arms.Match plugin, discovery, suites, budgets, trim
rtk dotnet fsi build.fsx -- test --group analyzers  # analyzer unit tests and truth fixtures

--quick skips npm installs, Chromium installation and restores. Other commands are build, analyze, format, format --dry-format, pack, docs, bump and shipit. publish --dry-publish validates and packs without uploading. Run --help for details.

Working across repositories

rtk dotnet fsi build.fsx -- dev local
rtk dotnet fsi build.fsx -- dev local --with-css
rtk dotnet fsi build.fsx -- dev packages

dev local uses ../Ranvier (and, with --with-css, ../Ranvier.Css), cloning a missing checkout, and writes the ignored Local.Build.props. --ranvier-root and --ranvier-css-root select other locations. Existing checkouts are never reset or updated. dev packages returns to the pinned NuGet versions in Directory.Build.props. For a one-off build, pass -p:UseLocalRanvier=true -p:RanvierRoot=<path>; Local.Build.props.example configures an IDE manually.

Releases

Each package has a ShipIt changelog with a project version updater. Trusted NuGet publishing and GitHub permissions are described in CONTRIBUTOR.md.

A change spanning the core and the views is validated in local mode at explicit revisions first. Release the core, wait until its version restores from NuGet, update RanvierVersion here, run every gate in package mode, then release the views.