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

@apparts/redux

v2.0.2

Published

Apparts Redux Boilerplate

Downloads

12

Readme

#+TITLE: Redux-Boilerplate #+DATE: [2019-02-07 Thu] #+AUTHOR: Philipp Uhl

  • Usage

Install =@apparts/redux=, create a file =store.js=:

#+BEGIN_SRC js import configureStore from "@apparts/redux";

import firststore from "./firststore"; import secondstore from "./secondstore"; // ...

const { store, persistor, types } = configureStore({ firststore, secondstore });

export { persistor }; export default store; #+END_SRC

** Stores

A store must export an object with:

  • =reducer = :: A function that takes the action-types as an argument and returns the reducer.
  • =actionNames = :: An array with all names of action-types of that store.
  • =blacklisted <?boolean>= :: /Optionally/, you can specify a =blacklisted= value. If true, the store will be put in the blacklist for persisting. That means, the store will then not be persisted.

*** Filestructure

A store should be in a subdirectory of the =store.js= file. A sensible filestructure could be:

  • src
    • redux
      • store.js
      • firststore
        • index.js
      • secondstore
        • index.js
        • actions.js
        • reducer.js
    • ...rest of your project

Small stores can be put in a single =index.js= file, larger stores should be split into separate files for actions and reducers.

*** Single file store Below is an example for the =index.js= of a store:

#+BEGIN_SRC js export const setOffline = () => ({ type: "SET_NETWORK", state: false, });

export const setOnline = () => ({ type: "SET_NETWORK", state: true, });

const actionNames = [setOffline().type];

const defaultState = true; const reducer = (types) => (state = defaultState, action = {}) => { switch (action.type) { case types.SET_NETWORK.name: return action.state; default: return state; } };

export default { reducer, actionNames, blacklisted: true, }; #+END_SRC

*** Multi file store

An example for the =index.js= of a store, that is split into multiple files: #+BEGIN_SRC js import reducer from "./reducer"; import actionNames from "./actions"; export * from "./actions"; export default { reducer, actionNames, }; #+END_SRC