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

@fluid-genui/core

v0.1.1

Published

Schema definition, IR types, and Zod validation for Fluid — the personalized-UI infrastructure.

Downloads

60

Readme

@fluid/core

Schema definition, IR (intermediate representation) types, and Zod validation for Fluid — the LLM-driven personalized-UI infrastructure.

This package is the specification layer. It is what the engine validates LLM output against and what the renderer walks. It has no runtime deps beyond Zod and is safe to import in both server and client code.

Install

npm install @fluid/core
# or
bun add @fluid/core

What's exported

import {
  defineSchema,
  validateIR,
  checkIRAgainstSchema,
  type FluidSchema,
  type FluidIR,
} from "@fluid/core";
  • defineSchema(...) — declare entities, endpoints, mutations.
  • validateIR(unknown) — Zod-parse arbitrary input into a FluidIR.
  • checkIRAgainstSchema(ir, schema) — semantic check (no undeclared fields, valid endpoints, etc.).
  • IR node types: Stack, Split, Grid, List, Kanban, Card, Stat, Heading, Field, Badge, Action.

Why a separate package?

The IR is the security boundary between LLM output and rendered components. Keeping the spec, the validators, and the types in their own dep-light package means:

  • The engine (@fluid/engine) can import it server-side without dragging React.
  • The renderer (@fluid/react) can import it client-side without dragging an LLM SDK.
  • Third-party adapters (custom caches, custom providers) can validate IRs without a heavy dep cone.

See the project README for the full architecture.

License

MIT