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

woo-sync

v1.0.29

Published

[![Build Status](https://travis-ci.org/stabinsh/woo-packages.svg?branch=master)](https://travis-ci.org/stabinsh/woo-packages) [![Coverage Status](https://coveralls.io/repos/github/stabinsh/woo-packages/badge.svg?branch=master)](https://coveralls.io/github

Readme

Woo-Sync

Build Status Coverage Status npm version

A helper for React/Mobx project.

It provides more handy way to access values in Mobx store from your <Component />.

Installation

$ yarn add woo-sync

Or

$ npm install woo-sync

Usage

The woo-sync package contains two separete packages SyncProvider and syncData

SyncProvider

Initially the React tree should be wrapped with SyncProvider.

SyncProvider is a wrapper component which passes store through context to all children components.

import React from 'react';
import ReactDOM from 'react-dom';
import { SyncProvider } from 'woo-sync';

import store from '../mobx-store';
import MyComponent from '../MyComponent';

const App = () => (
   <SyncProvider store={store}>
    <MyComponent />
   </SyncProvider>
);


ReactDOM.render(<App />, node);

syncData

To pass needed store values to <MyComponent /> we need to use syncData HOC component to wrap <MyComponent />.

import { syncData } from 'woo-sync';

const MyComponent = (props) => [
  <div>{props.name}</div>,
  <button onClick={props.changeName} type="button">Change name</button>
];

export default syncData({
  name: ['user', 'name'],
  changeName: ['user', 'changeName']
})(MyComponent);

Two ways of passing data to syncData is using plain object or callback function

Plain Object
syncData({
  name: ['user', 'name'],
  changeName: ['user', 'changeName']
})(MyComponent)
Callback function
syncData((props, state) => { // Arguments are current props and mobx store from context
  return {
    name: ['user', 'name'],
    changeName: ['user', 'changeName']
  };
})(MyComponent)

Mobx store looks like this :point_down:

import { action, computed, observable } from 'mobx';

class User {
  @observable username = null;
  
  @action changeName() {
    this.username = 'John';
  }
  
  @computed get name() {
    return this.username;
  }
}

export default { // will be passed as a prop to SyncProvider
  user: new User()
};

:bear: :tiger: :octopus: :snail: :squirrel: