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

@type-r/react

v4.1.0

Published

React bindings for Type-R/models

Downloads

67

Readme

Using with React

Local component state

hook useModel( ModelClass )

hook useCollection.of( ModelClass )

class State = attributes({
    counter : 0
});

const StatefulComponent = () => {
    const state = useModel( State /* any model class */ );
    
    return (
        <button onClick={ () => state.counter++ }>
            { state.counter }
        </button>
    );
}
class Counter = attributes({
    counter : 0
});

const StatefulComponent = () => {
    const counters = useCollection.of( Counter );

    const selected = useCollection.subsetOf( counters );
    
    return (
        <div>
            <div>{ user.counter }</div>
            <button onClick={ () => user.counter++ }>Add</button>
        </div>
}

Data binding

class Linked

hook useLinked( value )

const StatefulDataBound = () => {
    // Obtain linked local state.
    const $name = useLinked( '' );

    return (
        <div>
            <input {...$name.props} />
        </div>
    )
}
 

model.$

@define class Book extends Model {
    static attributes = {
        name : '',
        author : ''
    }
}

const EditBook = ({ book }) => {
    // Obtain linked model attributes.
    const { name, author } = book.$;

    return (
        <div>
            <input {...name.props} />
            <input {...author.props} />
        </div>
    )
}

collection.$includes( model )

static Linked.value( value, set )

Normalized data and stores

Store is the subclass of Model used as a root to resolve id-references in 'normalized data structures', when the data is represented as a set of collections with items referencing each other by id. If you don't have normalized data structures, you don't need Store.

Attributes of types Model.memberOf( 'store.someCollection' ) and Collection.subsetOf( 'store.someCollection' ) will resolve model ids to the models taken from someCollection belonging to the closest Store model. The closest store is located as follows:

  1. The first Store from the model's owners chain is taken first.
  2. If there are no such a collection in it, the next Store class in ownership chain is taken.
  3. If there are no stores left in the ownerhip chain, the Store.global is used.

From the particular model's view, there's a single store namespace which is defined by Store.global and extended by upper stores in its ownership chain.

In @type-r/react, you can create the store as a local component state, and expose it down to the component subtree so its children can opt to use this context store for id resolutions in their local state models.

That leads to a multi-tier store achitecture where the next tier store may override upper store collections and extend it with new collections.

  • Tier 1. Store.global holds the state which is shared across all SPA pages.
  • Tier 2. Page component stores holds the state which is related to particular pages.
  • Tier 3. Particular components might add their local stores extending the namespace created by upper stores.

Stores

const X = () => {
    const state = useModel( State );
    useContextStore( state );
}