FAQ

Not really. tiny-engine-core is for sprinkling behaviour onto server-rendered HTML. If you need a full SPA with client-side routing and reactive rendering, reach for a real framework. If you need a small way to wire up a dropdown, you're in the right place.

Yes. The runtime never touches the DOM until UI.init() runs, and it reads existing markup rather than rendering it. So it works with anything that produces HTML - Rails, Django, Astro, Next.js RSC, plain static HTML.

Yes. The package ships .d.ts files. Capsule, CapsuleStore, and the engine surface are all typed.

It would dwarf the runtime. tiny-engine intentionally stays imperative - you mutate refs directly. For most data-attribute UI patterns, that is faster and simpler than a VDOM diff.

Use one UI registry per page, and call UI.config({ prefix }) before UI.init() when you need a custom attribute namespace for embeds or widgets.