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

@_linked/shape-ui

v2.5.1

Published

UI driven by a shape: editors, a table over any shape's instances, a form derived from its properties, a read-only view and a relation picker — plus the read and write paths through the Linked Query DSL.

Readme

@_linked/shape-ui

UI driven by a shape.

Each component takes a Shape and a property shape and renders a control for it — a text field, a select, a date picker, an avatar. It works on any shape, not a known one, which is the whole point: an application that adds a property gets an editor for it without writing one.

<TextfieldEditor of={person} property={givenName} />

Where it sits

| Layer | Package | Knows about | |---|---|---| | Design tokens | @_linked/css | nothing | | Headless components | @_linked/primitives | the DOM and the tokens | | Data binding | @_linked/react | shapes and queries; ships no components | | Shape-driven UI | @_linked/shape-ui | how to render an arbitrary shape | | Product surfaces | applications | one product's domain vocabulary |

Everything here renders a @_linked/primitives control and adds the shape binding. Nothing here knows about a specific product.

Consume this layer rather than rebuilding it. A product that needs a shape-driven form field extends what is here; growing a second implementation inside an application is how the same component ends up existing three times, and then drifting.

Why the name changed

This package was @_linked/ui. That name said only "not backend" — the least informative label available for the layer most in need of one that states its contract. shape-ui says what it is.