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

localstate

v0.1.0

Published

Make your models observable. Nothing more nothing less. However, the interesting part of Mvstate lies in how this is done. It's using the functor concept from functional programming to achieve this.

Downloads

1

Readme

Mvstate

Make your models observable. Nothing more nothing less. However, the interesting part of Mvstate lies in how this is done. It's using the functor concept from functional programming to achieve this.

Mvstate allows you to wrap your model, and then lift your normal functions to operate on your wrapped model. This means that your functions stay completely ignorant of all the observable magic. Let's have a look:


// Model
const create = () => ({counter: 0});
const inc = ({counter}) => ({counter: counter + 1});
const dec = ({counter}) => ({counter: counter - 1});

// Now wrap you model in an Observable
const observable = mkObservable(Model.create())

// Observe it
observe(observable, (newObservable) => {
    console.log('value is', getModel(newObservable).counter);
})

// Operate on your observable. Note: functor laws are obeyed to avoid nasty surprises!
const newObservable = fmap(inc, observable);

// When you want, notify all observers that your observable changed.
notify(newObservable); // "value is 1" will be logged.

If you look at the above example and get scared or confused, don't worry! This is the core code, it is not how you are intended to use it. Just notice that the three lines that make up the model are very simple and ignorant of any observable behavior.

Have a look at the React examples for how it is used in real life. It's pretty fancy!

To sum up, Mvstate allows you to make your models observable. But while coding your models, you can completely ignore that they are observable. No need to mess with state. No need to keep track of a list of observers. Just code your elegant pure code operating on immutable models. Mvstate isn't solving a hard problem, but it can help you produce better and more maintainable code. Try it out and join me in the quest of raising the quality of code!

Cheers, Peter Crona