Appearance
How it works
These pages explain how Tessera is put together and why. You do not need them to use it.
- The compile pipeline: from a
.tessfile to a module. - The signals runtime:
state,derivedandeffect. - The renderer adapter: how a template becomes elements.
- CSS layers and scoping: where styles go and why they cannot collide.
- Auto-import resolution: how a tag finds its component with no runtime registry.
- The route manifest: how a folder of pages becomes routes.
- Why contracts and enforcement: the reasoning.