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

paramus

v2.1.1

Published

State store for small web applications

Downloads

16

Readme

Tests: CircleCI

Paramus

Paramus is a state store for small web applications, with the goal to work in any stack in with any limitations. The purpose of Paramus is to provide persistent state storage in a none-intrusive way.

For example if your app relies on localstorage, then Paramus can run on the session storage. Or if your app relies on both local- and sessionstorage, then Paramus can run on the url, or in a cookie.

No matter what technologies your app uses, Paramus should be able to find a vacant technology to use for it self.

Demo Fiddle (WIP)

NPM

npm i --save paramus

CDN

<script src="https://unpkg.com/paramus"></script>

API

Paramus(storeId: string, initState: T, onChange?: (state: T) => void): T

import { Paramus } from 'paramus';

/* url | object | <Paramus.extend> + planned "cookie | localStorage |sessionStorage | indexedDB | webSQL"  */
const state = Paramus('url', {
   foo: 3, 
   bar: 42
}, newState => {
   // Triggers whenever a value is changed, ex: state.foo = 7
});

console.log( state.foo ); // 3
state.foo = 7;
console.log( state.foo ); // 7

Adding your own store

Paramus.extend(newStore)

Paramus.extend({
   id: 'object',
   init(initial: object) {
      // Called when a new instance of Paramus is created
      // initial is the state object passed to Paramus
   },
   get(key: string): any {
      // Called whenever a parameter is read from 
   },
   set(key: string, value: any) {
      // Called whenever a parameter is assigned to
   }
});