What each @motionactor/* package owns, and which ones an application actually installs.
The @motionactor/* line is published to GitHub Packages. Most applications install two
packages: the runtime and one backend. The actor families themselves are not on this list —
they are copied into your repo from the component library.
A backend turns resolved actor state into pixels. The release target is DOM/React through
Remotion; the others are retained while their longer-term ownership is undecided.
@motionactor/remotion
Optional Remotion composition, frame, readiness, and canvas adapters.
@motionactor/dom
DOM backend: actor renderers, the SceneRenderer wrapper, and the DOM effect compositor.
@motionactor/react
React renderer surface. Currently re-exports the DOM backend, so importing either is equivalent.
@motionactor/three
Three.js renderer backend for 3D scenes.
@motionactor/pixi
Pixi backend — layer host plus the cross-renderer surface contract.
This repository is the runtime. Two sibling repositories own the rest:
motionactor
the runtime, backends, Remotion integration, the published package line
motionactor-library
reusable actor families
the shadcn-style registry at docs.motion.actor/r/motionactor
studio and showcase apps
motionactor-lab
capture packages, scene input, artifact storage, private experiments
A runtime change a family needs lands and publishes here first; the library then bumps its
pin. Because the library builds against published versions rather than linked sources,
every library build re-tests the packaging seam.