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

react-jsplumb

v0.1.3

Published

This is a base implementation of wrapping jsplumb with react + redux to be more usable in a react based environment

Readme

react-dag

This is a base implementation of wrapping jsplumb with react + redux to be more usable in a react based environment.

Install

npm install react-dag

Usage

  import {DAG} from 'react-dag';
  class MyComponent extends Component {
    ...
    render() {
      return (
        <DAG settings={this.settings}
            data={this.data}
            enhancers={this.enhancers}
            additionalReducersMap={this.additionalReducersMap}
            middlewares={this.middlewares}/>
      );
    }
  }

Props

  • settings - Settings to be used for JsPlumb. Check out dag-settings.js for base settings that are available.
Note
The `settings` prop is like either or - Either you provide the entire settings for the DAG or take the base settings. I am still yet to work on how to achieve granularity (or mixin) multiple different settings.
  • data - Is the initial state of the DAG. Could be used to render the DAG right away if the data is already available (instead of constructing the DAG one node at a time).

  • enhancers - Are the list of enhancers you would want to add to the dag-store. To read more about enhancers please check the documentation here

  • additionalReducersMap - The DAG comes with a base reducer that does some base operations. If you want additional reducers to be used for any property of the store you could pass in the map and the reducers would get reduce'd (as in executed one at a time. Something like reduce reducer)

    For instance the store right now has a structure like,

    {
    nodes: nodesReducer,
    connections: connectionsReducer,
    graph: graphReducer
    }

    In addition to the the nodesReducer if there are additional reducers that you want to add then it could be passed in as something like this,

    {
    nodes: [myReducer1, sometherReducer2]
    }

    Based on the additional reducer the above implementation of redux store's reducer becomes,

    {
    nodes: nodesReducers
            .reduce((prev, curr) => curr.bind(null, prev(state, action), action))(),
    connections: connectionsReducer
            .reduce((prev, curr) => curr.bind(null, prev(state, action), action))(),
    graph: graphReducer
            .reduce((prev, curr) => curr.bind(null, prev(state, action), action))(),
    }
    Note

    This is a little crude as of now. Will have to see if I can use this as a generic functionality for any store.

  • middlewares - Similar to additionalReducers you could pass in additional middlewares that you want to add based on your reducers.