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

fluxxor-autobind

v0.2.0

Published

AutoBind plugin for Fluxxor to help prevent spaghetti props wiring.

Downloads

17

Readme

Fluxxor-AutoBind

An auto-binding plugin for Fluxxor to prevent spaghetti props wiring.

Usage

Usage requires three simple steps:

  1. Install AutoBind after initializing Flux.
var flux = new Fluxxor.Flux(stores, actions);
require('fluxxor-autobind').install(flux);
  1. Specify properties you want to expose in your stores.
var ExampleStore = Fluxxor.createStore({
  // This is the only piece of configuration you need to add. 
  // Names must be unique, and must be equal to the property 
  // name on the store.
  autoBind: ['foo', 'bar'],
})
  1. Reference these properties in your views.
var DeeplyNestedView = React.createClass({
  mixins: [
    // Flux must be available to the view.
    FluxChildMixin, 
    // Specify the properties you want to be bound to this 
    // component's state.
    AutoBind.Mixin('foo', 'bar') 
  ],
  render: function() {
    return <div>{this.state.foo + " " + this.state.bar}</div>;
  }
})

Rationale

When developing a Flux application, over time you can end up with a ton of properties going from your root component down to deeply nested components. It can make adding simple properties to your stores and getting them to your components very complicated, as each intermediate component has to pass the prop down. And, unless your app is using immutable values, shouldComponentUpdate can start to get massively complicated.

Fluxxor's solution for this is to use StoreWatchMixin and getStateFromFlux to accomplish this.

I have found in practice that this is error-prone (ever forget to specify the store's name in StoreWatchMixin?) and could be simplified via a simple property registry. Since property names are (usually) unique per store, it makes sense to enter them into a registry hosted on the Flux instance and simply reference them by name.

The result is a very simple setup that only requires a few small changes every time you add a property and want to reference it in your components.

Example

https://strml.github.io/fluxxor-autobind/ (View Source)