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

loco-cache

v1.0.2

Published

cache data using browser session storage

Downloads

147

Readme

loco-cache - front-end caching using browser local storage

npm package

Usage

Purpose

Sometimes a website's performance can be greatly improved if commonly used data is cached on the front end. Most browsers provide APIs to allow storing data on session or domain level. loco-cache provides a robust abstraction on top of the storage APIs to make caching simple. It provides the following features:

  • Caching with expiration - each key can be automatically expired
  • Sweep - automatically removes old entries to free up storage space
  • Collision prevention - keys are prefixed to avoid name collision with other packages
  • Optional compression - supports optional compression to save storage space

Documents

Examples

loco-cache API is intuitive yet customizable.

Example 1: basic example using .get() and .set()

var cache = require('loco-cache')()

// assume we have to obtain a list of countries via AJAX to populate a dropdown
// before the AJAX call, check the cache first
var countries = cache.get('countries')
if (countries == null) {
    // not in cache, maek the AJAX call instead, then store in cache
    countries = await ajax('/api/countries').data
    cache.set('countries', countries)
}

Example 2: customize with options

var cache = require('loco-cache')({
    prefix: "acme",
    expiresIn: 1200,     // each key expires in 1200 seconds
    storage: 'local'  // use local storage
})

// only customization is different. everything below stays the same
var countries = cache.get('countries')
if (countries == null) {
    // not in cache, maek the AJAX call instead, then store in cache
    countries = await ajax('/api/countries').data
    cache.set('countries', countries)
}

Cheatsheet

Simple cheatsheet to get you going. For detailed documentation please visit Docs

var cache = require('loco-cache')(options)

  • options - options to customize the cache. If null, default values are used
    • prefix - prefix used for each key to avoid name collision. default: loco
    • expiresIn - how many seconds to keep a key in cache. default: 600
    • storage - session or local storage. default: session

cache.get(key)

  • key - needs to be a string, cannot be null
  • returns the stored object

cache.set(key, obj)

  • key - needs to be a string, cannot be null
  • obj - a simple object to store