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 🙏

© 2026 – Pkg Stats / Ryan Hefner

ts-mobx-basic-stores

v0.8.3

Published

The collection of helpers written with mobx and typescript.

Downloads

22

Readme

Description

The collection of helpers :hammer_and_wrench: written with mobx :muscle: and typescript :heart: which helps you to simplify code and organize you application.

These are most :blue_heart: frequently used libraries in my reactjs/mobx projects.

Example

Click to the headers :point_down: to navigate to the example page.

Array

Represents the logic of an observable array. Control your collections with that store.

AsyncOperation

Represents the logic of an observable async operation. Useful for fetch/submit data from/to API.

You can easily control operation state based on OperationState, run operation in single instance and set up retries.

Boolean

Represents the logic of an observable boolean value.

Looks similar to ToggleState but semantically is more appropriate for boolean flags.

Cases for BooleanStore: phone.isActivated.true or car.isAvailable.false.

Cases for ToggleState: modal.visibility.isOff or lighter.power.isOn.

Disposer

Represents a container with callbacks (like mobx reactions or any others) that should be called later to perform some disposal.

You can fill the container in a runtime and call dispose-method accordingly to yours application lifecycle.

You can find a good example of usage with ts-mobx-form-state to dispose reactions.

Numeric

Represents the logic of an observable numeric value.

Object

Represents the logic of an observable object.

Useful in case of forms handling and representing complex data structures.

OperationState

Represents the logic of an observable operation state with typical transitions.

Helps to control the single operation flow and react to every state change.

Selection

Represents the logic of an observable selection.

Allows managing selection state. For the instance the checkbox lists or radio button lists.

String

Represents the logic of an observable string.

Timer

Simplify a timer workflow.

ToggleState

Represents the state of the toggle operation (on/off/indeterminate).

For the instance, helps to control the checkbox state.

Value

Represents the logic of an observable scalar value.

Installation

npm i --save ts-mobx-basic-stores

Code styles

Run npm run lint.

Tests

Run npm run test.

Roadmap

  • Get stable 1.0.0 release ready.

  • Segregate all stores to separate packages later when it's stable (As for now, all stores combined to single package to develop and maintain it faster).