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

little-store

v1.2.0

Published

Super simple curried storage in a given plain object when you just must have mutable state

Downloads

24

Readme

little-store

Super simple curried storage in a given plain object when you just must have mutable state

NPM

Build status semantic-release js-standard-style no sudden unpublish

Install and use

npm install --save little-store
const littleStore = require('little-store')
const o = {}
const setFoo = littleStore(o, 'foo')
setFoo(o, 42) // returns 42
// o is {foo: 42}

Why?

Mostly this is a convenient curried function for storing side data in promise chains. With most functions only taking and passing a single argument, storing intermediate values is a pain (see my blog post). Functional libraries like Ramda and Lodash have nice utilities for getting a property from a given object, like _.property, but I could not find a simple set property function. Ramda has lenses, but those return a new object (which is nice) and this is not what I needed. Thus I was forced to do something like this - make a closure just to keep data from the first call

function login () {
    return getUsername()
        .then(function (username) {
            return getPassword()
                .then(function (password) {
                    // check username and password
                })
        })
}

We can store the intermediate results from each promise in local mutable object

function login () {
    const state = {}
    return getUsername()
        .then((s) => {state.username = s})
        .then(getPassword)
        .then((s) => {state.password = s})
        .then(function () {
            // check username and password from state
        })
}

A lot more steps but smaller pyramid of promise doom.

With generators, this is a lot less code, but not as simple to start in most cases

function * checkPassword () {
    const username = yield getUsername()
    const password = yield getPassword()
    // check username and password
}

With little-store creating little "set" callbacks is simple (even multiple ones)

const store = require('little-store')
function login () {
    const state = {}
    return getUsername()
        .then(store(state, 'username'))
        .then(getPassword)
        .then(store(state, 'password'))
        .then(function () {
            // check username and password from state
        })
}

We can even avoid store(state, ...) boilerplate since the littleStore is curried

const store = require('little-store')
function login () {
    const state = {}
    const remember = store(state)
    return getUsername()
        .then(remember('username'))
        .then(getPassword)
        .then(remember('password'))
        .then(function () {
            // check username and password from state
        })
}

Related

Small print

Author: Gleb Bahmutov <[email protected]> © 2016

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2016 Gleb Bahmutov <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.