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

yarsc

v1.0.0

Published

yet another react state container. now in 65 lines or less!

Downloads

3

Readme

yarsc

yet another react state container. now in 65 lines or less!

usage

yarn add yarsc

YARSC is a state container built in only React APIs. It's been done a million times but whatever.

This state container provides out of the box support for thunks and has a very minimal logger when you're in dev mode (web or native).

Use <Provider /> to initialize the state context. Pass it a root reducer and an initial state and you're good to know.

You can use the useStateContext() helper to grab state and dispatch.

full example

import React from 'react'
import Provider, { useStateContext } from 'yarsc'
import nhlApi from '@nhl-api/client'

const teamsAction = () => async dispatch => {
  try {
    const response = await nhlApi.getTeams().then(data => dispatch({ type: "TEAMS", payload: data }))
    return Promise.resolve(response)
  } catch (err) {
    console.error(err)
  }
}

const teamsState = {
  teams: []
}

function teamsReducer = (state = teamsState, action) => {
  switch (action.type) {
    case "TEAMS":
      return {
        ...state,
        teams: action.payload
      }
    default:
      return state
  }
}

const fooAction = () => ({
  type: "FOO",
  payload: 2
})

const fooState = {
  foo: 1
}

function fooReducer = (state = fooState, action) => {
  switch (action.types) {
    case "FOO":
      return {
        ..state,
        foo: action.payload
      }
    default:
      return state
  }
}

const rootReducer = ({ teamsState, fooState }, action) => ({
  teams: teamsReducer(teamsState, action),
  foo: fooReducer(fooState, action)
})

const initialState = {
  teams: teamsState,
  foo: fooState
}

const App = () => {
  const { state, dispatch } = useSessionContext()

  React.useEffect(() => {
    dispatch(teamsAction())
  }, [])

  return (
    <div>
      <h1>{state.foo}</h1>
      <ul>
        <li>
          {state.teams ? state.teams.map(team => team.name)} : null}
        </li>
      </ul>
    </div>
  )
}

const Root = () => (
  <Provider reducer={rootReducer} initialState={initialState}>
    <App />
  </Provider>
)

built with skeletor 💀