jx

What problem does it solve?

JX provides clear patterns and validation for building reusable Jinja-based components so teams avoid brittle templates, missing imports, inconsistent assets, and per-request Catalog construction that causes performance and correctness issues.

Core Features & Use Cases

• Catalog best practices: guidance to create a shared Catalog singleton, register folders and packages, and reuse a Jinja environment.
• Component conventions: explicit import rules, TitleCased component filenames, a single def block, implicit content and attrs, named slots, and runtime type validation.
• Asset and integration workflows: declare CSS/JS per component, render assets from layouts, collect package assets at build time, and integrate with FastAPI, Flask, Django, HTMX, Alpine.js, and Stimulus.
• Validation and migration: use jx check for static template validation and follow a documented migration path from JinjaX to JX.

Quick Start

Render a page using a shared Catalog singleton and run jx check against your catalog to validate imports and templates.