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

substate-connect

v3.1.0

Published

Easily wire up substate with popular front-end libraries

Downloads

112

Readme

substate-connect

Higher Order Functions to use substate with React (soon Preact and Inferno)

Demo repo

Example usage

mapping state to props in component

import {connect} from 'substate-connect';
import substateInstance from './mystate.js';
/**
    MyComponent
*/

export default connect(substateinstance, {
    prop1: 'path.to.prop',
    prop2: 'name',
    prop3: 'location' 
    })(MyComponent);

### wrapping App in store instance
// App.js
import { Provide } from 'substate-connect';
import substateIntsance from './mystate.js';

/*

function App....

*/
const WiredApp = Provide(substateInstance, ["STATE_UPDATED"], onMount)(App);

export default WiredApp;

What the H does this do?

Similar to react-redux connect method.

You pass in a reference to the substate instance, so we can wire up the props, and you pass in an object mapping the prop names for the component (the keys), to the prop values you want (the path -- as a string -- to the chunk of state you need). Then it returns a function which needs your component as an argument.

The Provide HOC needs the substate instance as a first argument. The second argument is an array of substate $types you want the App to setState too. It's recommended to at least have "STATE_UPDATED" passed in the array.

onMount is a function that will fire when the Provide higher order component mounts. The signature: onMount(store, triggers) So you have access to the store and triggers passed in. Note: this is bound to the HOC.

Now it's all wired up.

Why map the props?

Mapping props allows your component to have its own prop structure and not care what the global state structure is like. This allows for component reusability.

What about props through composition?

Pass those in as you normally would. They will be alongside the props from the connect method. This way you can pass functions into the component during normal composition.