npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fluixi/jsx

v1.0.0-alpha.80

Published

JSX runtime types and factory for Fluixi — fine-grained, no virtual DOM.

Readme

@fluixi/jsx

The JSX runtime and types Fluixi compiles against.

License: MIT TypeScript npm JSX


This is the jsxImportSource for Fluixi: the jsx/jsxs/Fragment factories, the element helpers, and the JSX type definitions that give intrinsic elements and their attributes real types.

It is a small package with a narrow job. Most Fluixi code never imports it — the compiler turns JSX into direct DOM calls, so the factories are a fallback for anything it did not compile. Components, control flow, rendering and reactivity live elsewhere; see Where things actually live.

Installation

pnpm add @fluixi/jsx @fluixi/dom

Setup

Point TypeScript at this package and let the Vite plugin compile:

{
  "compilerOptions": {
    "jsx": "preserve",
    "jsxImportSource": "@fluixi/jsx"
  }
}
// vite.config.ts
import { fluixi } from '@fluixi/vite-plugin';

export default { plugins: [fluixi()] };

npm create fluixi wires both for you.

What it exports

| Export | Purpose | | --- | --- | | jsx, jsxs, Fragment | The automatic-runtime factories | | jsxDEV | The development factory | | createElement, cloneElement, isValidElement | Classic element helpers | | createRef, forwardRef | Refs | | renderToString | String rendering | | mergeProps | Merge prop objects, keeping getters live | | delegateEvents | Register delegated event types | | createReactiveJSX, jsxComponent, defineComponent, memo, hydrate | Lower-level integration seams |

Types: JSXElement, JSXComponent, JSXProps, RefCallback, RefObject, plus the global JSX namespace with intrinsic elements.

Where things actually live

This package is a runtime, not a framework façade. Reaching for it directly is usually a sign you want one of these instead:

| You want | Import from | | --- | --- | | Show, For, Index, Switch, Match, Portal, Dynamic, ErrorBoundary | @fluixi/core or @fluixi/dom | | render, hydrate (app entry) | @fluixi/core | | signal, memo, effect, store | @fluixi/reactive | | Server rendering | @fluixi/server, or @fluixi/start for the whole thing | | The JSX → DOM compile | @fluixi/compiler, @fluixi/vite-plugin |

Typing an element

The JSX namespace types intrinsic elements and their attributes, so a misspelled attribute or a wrong event handler is an error rather than a silent no-op:

const el = <input type="text" onInput={(e) => console.log(e.currentTarget.value)} />;
//                            ^ typed as InputEvent on HTMLInputElement

Reactive attributes accept an accessor as well as a value, which is what lets the compiler wire a binding without changing your types:

const count = $signal(0);
<div title={() => `count: ${count()}`} data-count={count()} />;

Refs

import { createRef } from '@fluixi/jsx';

function Field() {
  const input = createRef<HTMLInputElement>();
  onMount(() => input.current?.focus());
  return <input ref={input} />;
}

A callback ref works too — ref={(el) => …} — and both forms are typed bivariantly, so a component that takes HTMLElement accepts a more specific ref.

License

MIT

Links