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

v1.0.3

Published

MobX Store Provider Component Decorator

Downloads

306

Readme

mobx-provide

MobX Store Provider Component Decorator

semantic-release version MIT License travis build Codecov js-standard-style Commitizen friendly downloads

Description

Do you like the convenience of importing store directly to your MobX component, but find testing a bit tricky? With mobx-provide decorator, you can still retain your imports, pass the store as props through the decorator, and just prepend your store with props or this.props or use destructuring like const {store} = this.props before the return statement in your render() method.

The mobx-provide is a decorator or higher-order component, that accepts a store object and a component as inputs, and returns a (enhanced) component.

Usage

const store = {usersStore, articlesStore, adminStore}
const ObserverComponentWithStore = provide(store)(observer(Component))

or

const ObserverComponentWithStore = provide({
  usersStore,
  articlesStore,
  adminStore
})(observer(Component))

Example

With Direct Import

import React from 'react'
import { observer } from 'mobx-react'
import userProfile from 'stores/userProfile'

export class UserProfile extends React.Component {
  render () {
    return (
      <div>
        <h1>User Profile</h1>
        <p>Name: {userProfile.name}</p>
        <p>Email: {userProfile.email}</p>
      </div>
    )
  }
}

export default observer(UserProfile)

With Provide Decorator

import React from 'react'
import { observer } from 'mobx-react'
import userProfile from 'stores/userProfile'
import provide from 'mobx-provide'

export class UserProfile extends React.Component {
  render () {
    const {userProfile} = this.props
    return (
      <div>
        <h1>User Profile</h1>
        <p>Name: {userProfile.name}</p>
        <p>Email: {userProfile.email}</p>
      </div>
    )
  }
}

const ObserverComponent = observer(UserProfile)

export default provide({userProfile})(ObserverComponent)

The DIFF between the two

+ const {userProfile} = this.props
return (
  <div>
  ...
  </div>
)
- export default observer(UserProfile)
+ const ObserverComponent = observer(UserProfile)
+ export default provide({userProfile})(ObserverComponent)

There is not much difference between the two. You just have to reference the store using props: const {userProfile} = this.props

Testing

Basically, you have to have two exports for your component, named export and default export. Your named export could be the plain component for your testing, and the default export for enhanced or observer component.

In your test file, import the plain component, create a new instance of your store and pass it as props as you normally would. Simple!

Contributing

To contribute, please follow these steps:

  1. Fork the repo
  2. Make a branch for your change
  3. Run npm install
  4. Make your changes
  5. Run git add -A to add your changes
  6. Run npm run commit (Do not use git commit)
  7. Push your changes with git push
  8. Create the Pull Request
  9. All done and celebrate!

Contributors

Be the first to contribute!

License

MIT © Felipe Apostol