Kita

@ecopages/kitajs renders .kita.tsx Pages, Layouts and document shells to strings with @kitajs/html. It is the reference for how little an Integration has to declare: everything else comes from core's shared route and document-shell pipeline (Graph to HTML).

What it plugs into core

ContractKita
Plugin name / extensionskitajs / ['.kita.tsx']
DeclarationdefineIntegration({ name, extensions, jsxImportSource, renderer }), not a hand-written subclass
jsxImportSource@kitajs/html
RenderercreateIntegrationRenderer('kitajs') with no hooks
Build plugins (plugins())none
serverDomnone
bundlesPageDependenciescore default (false)
HMR strategynone; no hmr() override
Hydrationnone

defineIntegration builds an IntegrationPlugin subclass from the declarative fields and the renderer class. kitajsPlugin is both the factory and, through .Plugin, the class; KitaHtmlPlugin is a deprecated alias of .Plugin.

Renderer

createIntegrationRenderer supplies the whole route pipeline, and a renderer adds behavior through hooks. Kita registers none. Hooks are the extension point for a Kita-specific capability; subclass only when a hook cannot express it.

Mixed rendering

A Lit element a Kita Component declares with an ssr: true script gets its declarative shadow root on a Kita Page: core passes the document through Lit's server renderer (Lit). Kita is meant to be the outer shell. When a Kita-owned Page reaches a Foreign Child, core resolves that Foreign Subtree with the owning renderer and splices the HTML back in (Integrations and Foreign Children).

yesnoyesnoKita Page renders itsComponents to a stringReaches a Foreign Child?Owning renderer rendersthe Foreign Subtree, HTMLspliced back inDocument stringLit assigned an ssr: truescript?Lit renderCustomElementsadds declarative shadowrootsPage Package injected,document returned
  • The Component must list the child in config.dependencies.components. Ownership is validated from declared Dependencies during route preparation, not discovered from rendered HTML.
  • Route-level dependency resolvers can add Components at request time; they count for handoff.
  • Kita children of Kita do not go through a separate child serialization contract.

@ecopages/kitajs/eco-embed exports EcoEmbed, a thin Kita-JSX wrapper over eco.embed(component, props, children). Use it to render a foreign or same-Integration Component from a Kita file without inline mixed-JSX authoring.

Islands

Kita emits no Island Host markup of its own and ships no client runtime. Interactivity inside a Kita Page comes from a Component owned by another Integration, which stamps and hydrates its own host: see React, Lit and Ecopages JSX, and Islands and hydration for the shared contract.

See also

Sources

This page describes the code below.