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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sill/state

v0.0.3

Published

Library agnostic state management.

Downloads

5

Readme

@loll/state

Library agnostic state management.

Install

npm i @loll/state --save

Creating a Store

Create new stores by passing an initial state object to createStore:

import createStore from '@loll/state'

const store = createStore({
  count: 0
})

Actions

Create actions that mutate state using store.setState:

function inc () {
  store.setState(state => ({ count: state.count + 1 }))
}

Components

Attach state to components using the connect export from ./store.js. Import actions to mutate state:

/** @jsx h */
import h from '@loll/h'

const MyComponent = store.connect(state => ({
  count: state.count
}))((props) => {
  return (
    <div>
      <h1>The count is {props.count}</h1>

      <button onclick={inc}>Up</button>
    </div>
  )
})

Rendering

The store returns emitter methods. When setState is called, a shallow-compare checks the state object for differences. If one is found, an update event is emitted.

store.on('update', () => {
  // re-render application here
})

API

setState

Accepts an object or a function that returns an object.

setState({
  count: 12
})

// or

setState(state => ({
  count: state.count + 1
}))

getState

Returns the full state object.

getState() // { count: 12 }

connect

Accepts an function that returns a slice of state and returns a function that in turn accepts a component.

const Component = connect(state => ({
  number: state.count
}))((props) => {
  return <h1>The count is {props.count}</h1>
})

on & off

The store uses mitt interally to emit a single update event when the state is updated. It also exposes mitt's off handler, should you need it.

function render () {}

on('update', render)

off('update', render)

MIT