3.42K
total weekly downloads
33 packages
dailies-studio
The ship vehicle: a dev server booted inside the user's project (Vite middleware mode) so their deps, aliases and assets resolve natively. Component discovery, contract extraction with HMR re-extraction, sidecar meta, document persistence, scaffold.
@dailies-studio/brand
WS0: the brand kit — what a client's website says about how their brand looks. A deterministic page-side collector gathers evidence, one schema-constrained model call makes the judgement calls (which image is the logo, which colour is primary), and pure c
@dailies-studio/bridge
The async postMessage protocol between an editor chrome and a preview stage. Built once because there are TWO synchronous bridges (the editor's __studio and the scene editor's __shotStudio) and same-origin policy forbids driving either across origins.
@dailies-studio/canvas
Canvas editor data plane: the Doc2D schema (one tree of frame/stack/text/image/vector/embed nodes with per-node keyframe tracks), validation, migration, exposed-prop contract mapping, the React Canvas2DRuntime generated components mount, and deterministic
@dailies-studio/canvas-editor
The canvas editor chrome: prebuilt React app served static at /canvas by the merged studio server, so user tooling can never break it. Layers, inspector, keyframe timeline. The 2D stage lives in src/stage and is served ONLY through the project's Vite (use
@dailies-studio/contract
Prop-contract layer: ControlSpec type system, defineControls DSL, Standard-Schema normalization, deterministic contractHash, engine integration.
@dailies-studio/dashboard
Dailies — Project Home and the public pages, one static app with one rail. Served by BOTH the Worker and the local CLI: at /projects/, every document in your workspace as a card, listed from the index, so opening it never addresses a workspace object; and
@dailies-studio/editor
The editor chrome (plan §4.1): prebuilt React app served static at / by the dev server, so user tooling can never break it. Outline, inspector, dope sheet, curve/spring editor, transport.
@dailies-studio/effects
First-party effect library: tsl-textures generators auto-adapted into contracted react-three-fiber components (foundations.md §4 — effect = contracted component), rendered unlit on a viewport-filling plane through the WebGPU-first stage; plus Paper Shader
@dailies-studio/engine
Headless deterministic animation engine: document model, keyframe tracks, sampler. Zero dependencies.
@dailies-studio/extractor
Scaffolding-assistant inference: derives ControlSpec drafts from a component's TypeScript props via a long-lived language service. The resolved contract stays the source of truth — this only pre-fills it.
@dailies-studio/motion
Motion for code components as pure functions of the studio frame: tweens, springs, multi-stop interpolation, stagger orders, seeded randomness and stepped time, on the engine's own curves. Frame-exact forwards, backwards and out of order, locally and host
@dailies-studio/particles
First-party GLB particle emitter: a contracted react-three-fiber component whose emission is a pure function of (frame, seed) — seeded PCG32 + closed-form kinematics, never per-tick integration. Dogfoods the contract system's curve/gradient/asset kinds.
@dailies-studio/player
The runtime users ship (plan §5.2): AnimationPlayer + usePlayback around the SAME engine sampler the editor uses — byte-identical values by construction. Hard CI budget <14KB gz for the core entry; react >=18 is the only required peer. 3D lives behind the
@dailies-studio/primitives
First-party contracted DOM layer primitives (text, shape, image, logo, counter, device frame). These are the zero-install component vocabulary shipped templates are built from: a template that references only builtin modules needs no vendored source and n
@dailies-studio/runtime
The tiny runtime React surface shared by the harness, the particle emitter, and the future player: the studio clock context (deterministic frame/seconds, never wall time).
@dailies-studio/scene
Scene editor data plane: the SceneDoc schema, validation, migration, exposed-prop contract mapping, and deterministic codegen that emits a contracted Motion Studio component from a scene. The three.js runtime rides the same package; the /doc entry stays t
@dailies-studio/scene-editor
The scene editor chrome: prebuilt React app served static at / by `dailies scene`, so user tooling can never break it. Hierarchy, add-object palette, inspector, TSL drawer. The 3D viewport lives in src/viewport and is served ONLY through the project's Vit
@dailies-studio/shot
Shot lane data plane: the Doc3D schema (scenes of free-transform 3D layers with a per-scene camera and cinematic post), the block animation resolver, validation, migration, the Canvas2D layer rasterizer, deterministic codegen, and the three.js ShotRuntime
@dailies-studio/shot-editor
The shot editor chrome: a prebuilt React app served static at /scene by the merged studio server (the old /shot redirects there), so user tooling can never break it. The 3D stage lives in src/stage and is served ONLY through the project's Vite (pinned thr
@dailies-studio/templates
F7 template packages: the shipped 9:16 short-form motion templates plus the format, registry and deep-copy loader behind them. A template is a validated Document referencing only builtin modules, wrapped in a manifest that freezes what it was published ag
@dailies-studio/text
First-party text animation preset library (F3-D): split chars/words/lines + stagger, presets as pure (visibility, params) -> unit styles (identical in editor preview, both export tiers, and the player), the canonical per-frame state resolver every surface
@dailies-studio/transitions
First-party transition preset library (F3-B): CSS presets (pure (progress, params) -> operand styles, identical in editor preview, both export tiers, and the player) and the curated gl-transitions subset hand-ported GLSL->TSL for the WebGPU-first stage (.
@dailies-studio/tsl-textures
Vendored fork of tsl-textures@3.0.4 (Pavel Boytchev, MIT) carrying the perlin-noise/static-noise clamp fix.
@dailies-studio/ui
The inspector's property-widget cluster (NumberField, TextField, spec-driven PropControl, curve/gradient value editors, icons), extracted so other studio apps can reuse it. No store, no document — commits and scrub gestures route through caller-supplied h