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-component

v0.2.3

Published

Simplified React components via MobX

Downloads

13

Readme

mobx-component

Build Status Dependency Status devDependency Status

Installation

$ npm install --save mobx-component

What's all this now?

MobX with React is awesome, but it tends to push you towards having just a single prop per React component, because the top-level props cannot be @observable. For example suppose you have this model:

import { observable, computed } from 'mobx'

class XYZ {
  @observable x: number = 3
  @observable y: number = 9
  @computed get z() { return this.x * this.y }
}

You want to render it with a stateless function component which just takes x y and z props and renders them:

import * as React from 'react
import { observer } from 'mobx-react'

const Adder = observer<XYZ>(({ x, y, z }) => <span>{x} + {y} + {z} = {x + y + z}</span>)

Unfortunately this won't work; the properties get copied over and lose their "observability" before the render function is called by React. So instead you have to write it something like:

const Adder = observer<{ xyz: XYZ }>(({ xyz: { x, y, z }) => <span>{x} + {y} + {z} = {x + y + z}</span>)

Not quite as nice. Using this mobx-component you can write it the first way:

import { component } from 'mobx-component'

const Adder = component<XYZ>(({ x, y, z }) => <span>x + y + z = {x + y + z}</span>)

The resulting Adder component has a single prop model: XYZ, so you would use it like so:

import { render } from 'react-dom'

const xyz = new XYZ()

ReactDOM.render(<Adder model={xyz} />)
// renders: <span>3 + 9 + 27 = 39</span>

xyz.x = 4
// renders: <span>4 + 9 + 36 = 49</span>