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

reastore

v0.9.6

Published

Dead simple state management for React

Downloads

33

Readme

ReaStore

Build Status

This is a proof of concept for an extremely simple and powerful state management library for React. It is inspired by state management mechanism of React components.

How it works

The library consists of three constructs:

  1. Store: Store is a base class that supposed to handle the state management code. The api is almost like React components' state management (a setState method and a state property that holds the state). You can subclass stores from Store, define methods which change the state and assume that your components will react based on changes on state.
export class GithubReposStore extends Store<GithubReposState> {
  constructor() {
    super();

    this.state = {
      username: "alisabzevari",
      repos: [],
      isLoading: false
    };

    this.fetchRepos = this.fetchRepos.bind(this);
  }

  fetchRepos(username) {
    this.setState({ isLoading: true, username });
    fetch(`https://api.github.com/users/${username}/repos`)
      .then(response => response.json())
      .then(result => {
        this.setState({ repos: result, isLoading: false });
      });
  }
}
  1. connect: It is like connect function in Redux. It creates smart components from dump ones. Simply write a mapStoresToProps function accepting stores and returning props of the component:
import { connect } from "reastore";

class GithubRepos extends React.Component {
  ...
}

const mapStoresToProps = ({ githubReposStore, sessionStore }) => (
  {
    username: githubReposStore.state.username,
    isLoading: githubReposStore.state.isLoading,
    repos: githubReposStore.state.repos,
    fetchRepos: githubReposStore.fetchRepos,
    changeCurrentUser: sessionStore.changeCurrentUser
  }
);

export default connect(mapStoresToProps, GithubRepos);
  1. Provider: Which is a very simple dependency container. Just Use this component on your application level and assign all stores to its value property.
import { Provider } from "reastore";
import { allStores } from "./stores";

const App = () => (
  <Provider value={allStores}>
    <GithubRepos />
  </Provider>
);

You can look at the example directory for a complete working example.