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

@field-ui/field-ui

v0.3.1

Published

Alias for @field-ui/kit — one install for the whole field-ui suite. Prefer @field-ui/kit, or install the individual @field-ui/* packages directly. (The engine itself is @field-ui/core.)

Readme

@field-ui/field-ui

An alias for @field-ui/kit. The bare field-ui name on npm belongs to an unrelated project, so the field-ui suite lives under the @field-ui scope. This package exists only so that @field-ui/field-ui resolves to the whole suite for anyone who reaches for it by name.

Install

npm i @field-ui/field-ui

This pulls in @field-ui/kit, which depends on every @field-ui/* package. Then import from the specific package you need (see the kit README).

Prefer the direct names:

  • The engine is @field-ui/core.
  • The whole suite is @field-ui/kit.
  • Or install just the adapter you need: @field-ui/elements, @field-ui/react, @field-ui/vanilla.

field-ui.com