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

simmutable

v2.1.0

Published

An immutable store using normal javascript

Downloads

19

Readme

simmutable

A simple immutable store.

How to use

const createStore = require('simmutable')

const store = createStore()

store.get() // {}

store.set({a: 1})
store.get() // {a: 1}

store.clear()
store.get() // {}

Api

config

Currently there is only one config variable

store.config.shouldFreeze = true

By default the store will ensure that all objects and nested objects are frozen in the store. Turning this off will not automatically unfreeze the store. It is suggested that you only change this prior to doing any work with the store.

get()

store.get() will return the current value of the store.

set()

store.set(valueToMerge) Will merge the object passed in, into the current store. If the valueToMerge won't actually change any value in the store, no changes are actually made to the store. The change event will still be emitted. When valueToMerge has n nested objects, it will determine what values actually changed, and ensure only those values, and their parents all the way up to the root are changed. This makes it much easier to determine from the root whether or not any changes were actually made to the store.

clear()

store.clear() will reset the store to it's initial value of {}. This will emit a change event.

EventEmitter

The store implements the prototype of an event emitter and will emit a change event any time the store is changed either by calling clear() or set()