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

@nexaiform/formily

v0.1.1

Published

NexAiForm Formily adapter: compiles the engine IR to a Formily schema and renders it with React. React and Formily are host-provided peers so only one runtime instance exists.

Readme

@nexaiform/formily

NexAiForm Formily adapter: compiles the engine IR to a Formily schema and renders it with React.

React and Formily are peer dependencies, never bundled. The host must provide exactly one runtime instance of each — two copies of React or @formily/core show up as Invalid hook call or silently lost Formily state.

| Peer | Range | | --- | --- | | react, react-dom, react-is | ~19.2.4 | | @formily/core, @formily/react, @formily/reactive-react | ~2.3.7 |

pnpm add --save-exact @nexaiform/formily @nexaiform/core @nexaiform/schema
pnpm add --save-exact [email protected] [email protected] [email protected]
pnpm add --save-exact @formily/[email protected] @formily/[email protected] @formily/[email protected]
import { NexAiFormRenderer } from "@nexaiform/formily";

<NexAiFormRenderer document={prepared} fieldDecorator={HostFieldDecorator} />;

The build keeps the "use client" directive, so the package works inside a Next.js App Router server-component tree. Conditions compile to Formily function reactions — no eval, so the host CSP never needs unsafe-eval.

ESM only, Node.js >=24.19.0. See the deployment guide for the full host runtime matrix and singleton checks.

Licensed under MIT.