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

jumpstore

v1.0.6

Published

A redux boilerplate saver

Downloads

4

Readme

jumpstore

npm

A redux boilerplate saver. Ever feel like sometimes your redux actions and reducers are unnecessarily verbose? While doing things as described in the redux docs makes the workings behind redux blatantly obvious, using this tiny module can cut down a LOT of code.

Installation

Install with npm:

npm install jumpstore --save

Then include it in your module:

es6:

import jumpstore from 'jumpstore'

or (commonjs):

const jumpstore = require('jumpstore')

Usage

The store replaces action creators and reducers (or rather, creates them for you all at once)

// store.js
import jumpstore from 'jumpstore'

const initialState = {
  pageTitle: 'This is the default',
}

// See "API" section below for info about these arguments
const store = jumpstore(
  'pageHeader', //the prefix for all actions in this "store"
  initialState,
  {
    setTitle(state, payload) { //action+reducer is combined, an action is created called `pageHeader_setTitle`
      return {
        pageTitle: payload
      }
    },
    //any other action/reducer you want
  }
})

export default store

Dispatch actions in your component the same as always:

import React from 'react'
import { connect } from 'react-redux'
import store from './store' //import this instead of your actions

const mapStateToProps = (state, ownProps) => {
  return {
    pageTitle: state.pageTitle
  }
}

const mapDispatchToProps = (dispatch, ownProps) => {
  return {
    changeTitle: (newTitle) => {
      //when calling actions (from the store above) you only need to pass in the payload
      dispatch(store.setTitle(newTitle))
    }
  }
}

const PageHeader = ({ pageTitle, changeTitle }) => (
  <div>
    <h1>{pageTitle}</h1>
    <button onClick={() => changeTitle('This is the new title')}>Change The Title</button>
  </div>
)

export default connect(mapStateToProps, mapDispatchToProps)(PageHeader)

Use redux combineReducers and createStore as usual:

//rootReducer.js
import pageTitle from './PageTitle/store'
export default combineReducers({
  pageTitle,
  //... other reducers (stores from jumpstore or regular redux reducers) here
})

API

jumpstore(<actionPrefix>, <initialState>, <actions>): Returns an object with action creators that can be called via dispatch

actionPrefix String:

All resulting action names are prepended with this string. If you use redux devtools chrome extension, you'll see each action defined in the 3rd argument is prepended with this string.

initialState Object:

The initial state for this store - reducers are applied to this state. Ex: { pageTitle: 'Default' }

actions Object:

Functions defined here become reducers, and action creators are exported for each one. Each function must return whatever changes are to be made - no need to return the entire state (via Object.assign), jumpstore does that under the hood similar to how react's setState works. For example:

{
  //the current state is received, along with the payload (whatever is normally provided to an action creator)
  setTitle(state, payload) {
    return {
      pageTitle: payload
    }
  },
  clearTitle(state){
    return {
      pageTitle: ''
    }
  }
}

When dispatching this action, you only need to provide the payload: dispatch(store.setTitle('New title'))

Origins

This was the seed module behind jumpstate but without all the hooks and effects and your components look exactly as they would if you were using regular ole redux (doesn't abstract dispatch)