Skip to content
Vincle
Esc

Loading…

    Server-side JSX renderer

    Your views in JSX.
    Your app in HTML.

    Compose typed, async components in your existing server. Start with an HTML response, then let slower parts of the page arrive when they are ready.

    npm install @vincle/core
    
    pnpm add @vincle/core
    
    bun add @vincle/core
    
    From JSX to HTMLTypeScript
    hello.tsx
    import { renderToString } from "@vincle/core";function App({ name }: { name: string }) {  return <h1>Hello, {name}!</h1>;}const page = <App name="world" />;const html = await renderToString(page);
    <h1>Hello, world!</h1>
    

    The rendered output is a plain HTML string.

    Supported runtimes
    • Node.js
    • Bun
    • Deno
    • Cloudflare Workers

    Start with one view.
    Grow with your page.

    Keep your server and routing. Choose how much rendering behavior each page needs.

    Defer the slow parts

    Add @vincle/flow to send the page shell first, then deliver deferred HTML fragments.

    Stream a fragment

    The page can arrive before the results.

    Keep the heading visible while an async component loads. With flow, a fallback fills the space until its HTML is ready.

    Choose how it is delivered: natively, or through an HTMX or Turbo adapter.

    Follow the complete example
    results-page.tsx
    // Results is an ordinary async component; the page opts in:function Page() {  return (    <main>      <h1>Search results</h1>      <Defer fallback={<p>Loading results…</p>}>        <Results />      </Defer>    </main>  );}const stream = renderToStream(() => <Page />, NativeAdapter);

    1 · The shell arrives first

    Search results

    Loading results…

    2 · The patch replaces the fallback

    Search results

    The patch, as sent on the wire
    <template data-for="fragment-1"><ul><li><a href="/guide/getting-started/installation">Getting started</a></li></ul></template>

    Built into the renderer.

    Typed views, predictable rendering, and explicit HTML boundaries.

    View source on GitHub

    Independent by design.

    One maintainer, a scope that stays small, and checks you can read for yourself.

    Built for a simpler need

    Vincle renders HTML on the server and stops there. Its scope is deliberate: views render to HTML without a virtual DOM, hydration or a reconciler.

    Read the comparison

    Feedback reaches the person who decides

    Issues and proposals are read by the maintainer who can act on them. A well-argued proposal can ship in the next release, as long as it fits the project's scope.

    Open an issue

    Public checks, with their limits stated

    Tests, differential fuzzers, mutation testing and comparative benchmarks are public, method included. They support specific claims; they are not an external audit.

    See the checks

    A focused tool you adopt view by view

    An MIT-licensed library you adopt view by view, keeping your server and routing. Rendering HTML imposes no client runtime; streaming can add a patch script, depending on the adapter. Its APIs are still a dependency, and porting views elsewhere is real work.

    Read the license