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

mobx-noclass

v1.0.1

Published

Create a mobx store without the use of es6 classes.

Downloads

9

Readme

mobx-noclass

Utility function to create a mobx store without the use of es6 classes.

Why?

I tend to stay away from ES6 classes. They do are convenient, but I have some issues with them:

  • They favor classical inheritance over prototypal inheritance.
  • They favor inheritance over composition.
  • They re-introduce the new keyword which comes from languages that works with classical inheritance and I feel that it strays away from JavaScript's true nature to make developers coming from Java, C++ and other similar languages more comfortable.
  • Creating private fields is either hacky or not elegant.

For more information, consult this awesome list.

Usage

createMobxStore(observables, actions)

Creates a new mobx store by passing the observables and the actions on the observables as objects.

Having the actions defined in objects will allow you to have closures that will serve as private fields.

Example

import { createMobxStore } from 'mobx-noclass';

let store = createMobxStore({
  value: 0,
  next() {
    return this.value + 1;
  },
  previous() {
    return this.value - 1;
  }
},
{
  inc() {
    return this.value++;
  },
  dec() {
    return this.value--;
  }
});