@exactjs/jsx
v0.7.0
Published
Compiler-only automatic JSX surface and TypeScript JSX declarations for eXact.
Readme
@exactjs/jsx
Compiler-only automatic JSX surface and TypeScript JSX declarations for eXact.
Configuration
{
"compilerOptions": {
"jsx": "preserve",
"jsxImportSource": "@exactjs/jsx"
}
}Applications normally receive this configuration from an eXact build integration. TSX must still pass through the eXact compiler; this package supplies the automatic JSX entry points and application-facing intrinsic element types.
JSX accepts regular, direct-view, and async authored component functions. The compiler normalizes durable components to the synchronous setup-plus-view runtime contract and lowers setup-local micro-component tags to lexical view calls.
Inside a component, <_target title="Details" /> places its implicitly supplied child with an owned
property contribution. Wrap several independently supplied children in an explicit fragment.
The package exposes the standard jsx, jsxs, and jsxDEV names so TypeScript and build tools can
resolve the automatic JSX convention, plus Fragment and the keyed-fragment marker. Those calls
are compiler input, not a VNode runtime: an uncompiled call fails immediately. DOM event props
preserve eXact interaction typing, and finite registry members remain ordinary JSX component
values. Namespaced attributes are accepted as compiler-owned source syntax. Use exactc --check
rather than raw tsc --noEmit when an application uses syntax such as component value/callback
bindings; the compiler validates the finite pair and checks its lowered TypeScript representation.
