Reference

Every module’s interface, generated by odoc from its .mli, where each function says what it does, what it refuses and what it defaults to.

The packages

Each JavaScript library bound is a package of its own, so an application installs only what it uses. A dune file names a library as it is installed (solidtype-kobalte); OCaml code names it as a module (Solidtype_kobalte).

Package	Libraries	What it is
solidtype	solidtype	Solid 1.9 bound whole, for Melange: signals, computations, resources, stores, its components and its renderer, server rendering included
solidtype-kobalte	solidtype-kobalte	Kobalte 0.13 bound whole, generated from its own declarations
solidtype-heroui	solidtype-heroui	HeroUI’s design ported by hand onto Kobalte’s components
ppx_solidtype	ppx_solidtype	The ppx that rewrites the JSX of .mlx files into calls Melange compiles
vite-plugin-solidtype	none: an asset of each GitHub release	The Vite plugin that turns those calls back into JSX for Solid’s compiler

solidtype

• Solidtype – Solid’s reactive core, its renderer in the browser and on the server, its stores and its components, one module each, and the JSX the ppx writes. The most read: Solid, Web, Server, Store, Jsx, Check and Html.

solidtype-kobalte

• Solidtype_kobalte – each of Kobalte’s components, part by part, its hooks and values, and Types, the types they name.

solidtype-heroui

• Solidtype_heroui – each port, one module each, and Styles, HeroUI’s variant functions, the classes of each look.

ppx_solidtype

• Ppx_solidtype – what each JSX form is rewritten to.