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

storken-actions

v1.0.3

Published

Add state-specific functions to a state which created by Storken.

Downloads

6

Readme

storken-actions

Add state-specific functions to a state which created by Storken.

Installation

# yarn
yarn add storken-actions

# npm
npm install storken-actions

Example

import { create as createStore } from 'storken'
import Actions from 'storken-actions'

const [useStorken] = createStore({
  plugins: {
    actions: Actions
  },
  storkenOptions: {
    tableData: {
      actions: {
        getUsers: (stork, userId) => {
          return fetch('https://myservice.com/user/' + userId)       
            .then(res => res.json())
        },

        getTransactions: (stork, userId) => {
          return fetch('https://myservice.com/transaction/' + userId)       
            .then(res => res.json())
        }
      }
    }
  }
})

Action functions behave just like getter functions. Its first parameter gives Storken object and the rest parameters are may be action-specific optional parameters.

Actions can also specify like this:

import { create as createStore } from 'storken'
import Actions from 'storken-actions'

const [useStorken] = createStore({
  plugins: {
    actions: Actions
  },
  storkenOptions: {
    tableData: {
      actions: (storken) => ({
        getUser: (userId) => {
          return fetch('https://myservice.com/user/' + userId)       
            .then(res => res.json())
        },

        getTransactions: (userId) => {
          return fetch('https://myservice.com/transactions/' + userId)       
            .then(res => res.json())
        }
      })
    }
  }
})

In this way, actions configuration of the state took a function that returns the actions. When the actions configuration is function (like this), the function's first parameter is storken object and the action functions get their own (action-specific) parameters directly.

License

Distributed under the MIT License.

Contribution

You can contribute by fork this repository and make pull request.