Selva Install

Build your own app

Everything the standalone @selvajs/selva app does also ships as npm packages, so you can drop the viewer, the controls, and the solve pipeline into a product of your own. Take this path when you want your own branding, routes, and domain model, with Selva doing the parametric work underneath.

The model

Build a normal SvelteKit app, add the @selvajs/* packages, and wrap them in whatever you’re building.

renders

reads/writes

sends inputs to

drives

speaks

speaks

solves over HTTP

Your routes, branding, domain logic

(the product you build)

@selvajs/ui

Svelte components + viewer shells

@selvajs/visualization

viewer core (three)

@selvajs/compute

Rhino.Compute client

@selvajs/schemas

schema types

@selvajs/platform + a provider

backend: auth, data, storage

Rhino.Compute

(your solve server)

Read it top-down. Your app is the product. It pulls in the Svelte layer (ui), the compute client, and a backend (platform + a provider) as building blocks. ui and compute both speak the same schema contract (schemas), visualization turns solve responses into Three.js objects, and compute is the only piece that talks to your Rhino.Compute server. Take only the boxes you need.

Building blocks

PackageGives you
@selvajs/uiSvelte components, theme, and the viewer/solve-session shells the Selva app is built from. Style to your brand.
@selvajs/visualizationThe framework-free viewer core: solve response → Three.js. three is a peer dep.
@selvajs/computeType-safe Rhino.Compute client. Turns inputs into solved geometry. No renderer. See below.
@selvajs/schemasSchema types and traversal helpers, so your app speaks the same contract as the plugin.
@selvajs/platform + a providerThe backend contract, plus an implementation of it. See Providers.

Mix and match. If you only want the viewer and solving inside an otherwise custom app, @selvajs/ui and @selvajs/compute are enough: ui peer-depends on visualization, solve, schemas, and three, so install those alongside it.

These are the ones you’ll reach for first, not the whole set. The packages page lists every @selvajs/* package with a link to its README and npm entry. Each README is the reference for its own API.

Getting started

These are ordinary npm packages. Install what you need, then point the compute client at your Rhino.Compute server (step 1).

pnpm add @selvajs/ui @selvajs/visualization @selvajs/solve @selvajs/compute @selvajs/schemas three
# + @selvajs/platform and a provider for Selva's backend model

Each package README covers its own imports and setup. @selvajs/ui is the best place to start; for solving, read on.

The compute client

@selvajs/compute talks to Rhino.Compute and nothing else; it has no renderer and no three dependency. It gives you:

  • Calls to Compute that return geometry, with errors you can narrow on instead of guess at.
  • Reading and writing Grasshopper data trees.
  • The same API in the browser and in Node.

Import from /grasshopper or /core, whichever you need, so a bundler drops the rest. The root export is empty on purpose, so importing from the bare package name gets you nothing.

Turning a solve response into Three.js objects is a separate job, and @selvajs/visualization does it. Import from /scene, /render, or /parse.

Full API reference: https://selva.dev/docs/api/compute/

Next