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

zowie

v1.2.5

Published

Simple API for HTML5 Local Storage

Downloads

5

Readme

zowie

Simple API for HTML5 Local Storage

Installation

npm install zowie --save

Overview

The subtle quirks of HTML5's Local Storage are replaced with a simple API that is intuitive to use and just gets the job done.

You may be wondering: Isn't localStorage's native API already simple to use? Why do I need to use Zowie at all? You certainly can use the native API, but you'll quickly discover that: 1) omg, I can only save strings? wtf?! and 2) I can't set an expiration time on the data? Again, wtf?! For you, my dear developer, Zowie takes care of these limitations lickety-split.

Usage and Examples

Zowie has two modes of operation: persistent (the default) or not.

If persistent (Zowie's default mode), then the browser's localStorage mechanism is used. Therefore, persistent mode is only for the browser. However, if persistent is set to false, then Zowie instead uses in-memory storage and thus can be used client or server side.

Import Zowie Module and Instantiate Object

There are three ways to instantiate the Zowie object, shown in the examples below.

// ES6 syntax (ES5 syntax example later in this document)
import Zowie from 'zowie';

// 1. a new Zowie object, no argument
//    will use localStorage
const Cache = new Zowie();


// 2. a new Zowie object with true arg
//    will use localStorage (explicit version of previous example)
const Cache = new Zowie(true);


// 3. a new Zowie object, with false arg
//    will not use localStorage, i.e., no persistence.
//    instantiating object this way allows use on the server.
const Cache = new Zowie(false);

Store and Retrieve Data

import Zowie from 'zowie';
const Cache = new Zowie();

// store
Cache.put('myKey', {a: 1, b: true, stuff: {n: [2, 3, 5], composer: 'Stravinsky'}});

// retrieve
const myData = Cache.get('myKey');

More About Retrieving Stored Data

Inspired by Python's get() method, an optional 2nd arg is available.

import Zowie from 'zowie';
const Cache = new Zowie();

// Retrieve a key which does not exist:
const myData = Cache.get('badKey'); // myData => null

// Retrieve a key which does not exist using an optional 2nd arg
const myData = Cache.get('badKey', {a: 1, b: 2}); // myData => {"a": 1, "b": 2}

Setting A Timeout

localStorage data typically remains available until it is manually deleted by the user.

However, sometimes we want our storage cache to last for a specified duration of time. Zowie allows a timeout value in seconds to be set. The timeout mechanism works in both persistent or in-memory modes.

import Zowie from 'zowie';
const Cache = new Zowie();

// After a key/value is Cache.put('myKey', myData), the data cannot be retrieved
// after 5 minutes has elapsed.
Cache.timeoutInSeconds = 300;

Utilities

keyExists(key) behaves thusly:

If no timeout is set (the default), then the method returns true if key exists, false otherwise.

However, if a timeout has been set, then keyExists() method behaves slightly differently. If no key found, returns false. If key exists and the timeout has not yet expired, returns true; if key exists and timeout indicates the cache for this key has expired, then the key is removed and returns false.

Cache.keyExists(key); // => boolean

removeKey(key), as its name suggests, merely removes the key if it exists. If the key does not exist, it's a no-op.

Cache.removeKey(key):

clear() removes all keys and data.

keys() returns a list of keys.

isLocalStorageAvailable() detects if localStorage is available.

This can happen, for example, if iPhone's Safari browser is in private mode, in which case you can either alert the user to turn off private mode or just reinstantiate the Zowie class with a false argument to use in-memory storage instead of localStorage:

Cache = new Zowie(false);

ES5: Instantiate the Zowie Class

If you're in an ES5 context instead of ES6, you'll need to use require instead of import.

The following assumes that you've got zowie v1.2.3+ installed. It uses the transpiled version of zowie that comes with the package (lib/index.js). I know, the following is a bit funky, but it should work.

var Zowie = require('./node_modules/zowie/lib/index').default;
var Cache = new Zowie();

Credits

Gerry Gold April 2016

Have fun!