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

dva-subscribe

v0.2.1

Published

A helper function to simplify the subscription of history in dva.

Downloads

12

Readme

dva-subscribe

Build Status Coverage Status NPM downloads

A helper function which can simplify the subscription of history in dva.

Usage

import subscribe from 'dva-subscribe'

// basic usage
// subscribe(history, dispatch, ...rules)

//in dva's subscriptions
subscriptions: {
    setup ({ history, dispatch }) {
        // you may code this before
        // history.listen (({ pathname, query }) => {
        //     if (pathname === '/index') {
        //         const {id} = query
        //         dispatch({ type: 'load', payload: {id} })
        //     } else if (pathname.startsWith('/a')) {
        //         const match = pathToRegexp('/a/:a/b/:b').exec(pathname);
        //         if (match) {
        //             const {name} = query
        //             dispatch({
        //                 type: 'fetch',
        //                 payload: { a: match[1], b: match[2] },
        //             })
        //             dispatch({
        //                 type: 'init',
        //                 payload: { name },
        //             })
        //         }
        //     }
        // })

        // now you can use following
        subscribe (history, dispatch, {
            url: '/a/:a/b/:b',
            queries: ['name'],
            actionCreator: (a, b, name) => [{
                type: 'fetch',
                payload: {a, b}
            }, {
                type: 'init',
                payload: { name },
            }]
        }, {
            url: '/index',
            queries: ['id'],
            actionCreator: (id) => ({ type: 'load', payload: {id} })
        })
    },
}

Api

subscribe(history, dispatch, ...rules)

  • @param history: Object: react-router history
  • @param dispatch: Function: dva's dispatch
  • @param rules: Array<Object rule> url rules, describe the pattern to match url and dispatch action
    • rule: Object url match option:
      • field url: String, the url pattern, etc '/a/:b/:c/x'
      • field queries: Array, default: [], list the queries you care, etc ['keyword', 'time']. If the pattern matches current url, only when queries you list or params in url are different with last url(if last url also matches the specified pattern) will the actionCreator executed and action dispatched, which is useful to avoid unnecessary dispatching.
      • field actionCreator: Function a function that will return action(s) you want to dispatch when url match and params/queries are different(if last url also matches).It will receive params and queries you speciafied as arguments: actionCreator(...params, ...queries)
      • field everyTime: Boolean optional, default: false, if true, the actionCreator will always be fired and the action it returns will always be dispatched as long as the url matches the pattern you specified.
  • @return unListen: Function to stop listening, call the function returned from subscribe()