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

@zerox-dg/mstate

v1.1.1

Published

A simple state management library for mithril.js

Downloads

2

Readme

mState

A dead simple state management library for Mithril.js

Install

npm i @zerox-dg/mstate

Why mState?

mState is a dead simple solution for state management for Mithril.js. While the core is really simple < 100 lines, mState is very flexible and it's actually only ~1kb minified.

Concept

The following diagram illustrate how mState works.

As you can see the global state can be modified using action called from the component or directly modifed by the component (for simplicity). That means you can completely drop the actions.

Example

The first step to do is to initialize a state and some actions.

CounterStore.js

import { makeState, registerState } from "mState";

const state = {
  counter: 0
};

const actions = {
  INCREASE(state, amount) {
    state.counter += amount;
  }
};

export default () => {
  makeState("CounterStore", state).withActions(actions);
};

App.js

import makeCounterStore from "./CounterStore";
makeCounterStore();
// mounting to #root/#app element...

After that you can inject it to any component with inject(). After injecting, the state will be available in vnode.attrs.

MyComponent.js

import { inject, callAction } from "mState";

const increaseCounter = vnode => {
  // you can modify state in 3 ways
  // action call with _call function in injected state
  vnode.attrs.CounterStore.counter._call("INCREASE", 1);
  // action call with callAction function from mState
  callAction("CounterStore", "INCREASE", 1);
  // directly modify the state
  vnode.attrs.CounterStore.counter += 1;
};

// closure component
const myComponent = () => {
  return {
    view(vnode) {
      const { counter } = vnode.attrs.CounterStore;
      return m(
        "h1",
        { onclick: () => increaseCounter(vnode) },
        `Counter: ${counter}`
      );
    }
  };
};
export default inject(myComponent, ["CounterStore"]);

Author

License

MIT