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

cachifyjs

v2.3.10

Published

CachifyJS is a js package to cache api responses and call them automagically and repeatedly. That can be controlled by parameters.

Downloads

43

Readme

CachifyJS

CachifyJS is a lightweight framework-agnostic npm package that helps you cache API responses data in the browser's local storage. By caching API responses, you can reduce the number of network requests and improve the performance of your frontend application built on any technology like: react, vue, angular, you name it.

Installation

npm install cachifyjs

Table of Contents

What's new! (v2.3)

  • key encryption

    Keys of the encrypted data will also be encrypted to ensure data security.

  • Wrapper around cached data

    The return from cachify or getCache functions or the received parameter of callback function of either the postSync or the after property is the cached data with a wrapper around it. Thus, it's structure is similar to the axios api response.

    If your cached data is like,

      const chachedData = {name: 'Ice cream', description: 'Cold'}

    Then the wrapper is like,

      const response = {data: chachedData}

    If no cached data there,

      const response = {message: "Data not found",nodata:true}

Guides

1. Caching API Response:

To use CachifyJS, import the cachify function into your JavaScript file and pass your API call to it. The cachify function will first check if the API response is already cached in local storage. If it is, it will return the cached data inside a wrapper (ex: {data: cachedData}), make the api call, cache the response data and run the callback. If not, it will make the API call, cache the response data in local storage and return the data.

Here's an example:

import {cachify} from "cachifyjs";

async function getProductList () {
    
    // configuration for api call
    const axiosConfig = {
        method: "GET",
        headers: { Authorization: `Bearer ${token}` },
        url: `https://www.yoursite.com/api/product/list?status=active`
    }

    // configuration for caching
    const cacheConfig = {
        key: `product/list?status=active`,//your own choice, recommended to keep it similar to your api uri
        errorCallback: handleError,
        lifetime: '1h',
        encryption: {
            secretKey: 'my-secret-key'
        },
        postSync: {
            callback: handleResponse,
            skipApiCallFor: '10s',
            syncTimeout: 1, //default (ms)
            syncInterval: '3h', //with time specifier
        },
    }
        
    try {    
        //GET request only
        let response = await cachify(axiosConfig, cacheConfig)
        //let response = await axios(axiosConfig)
        //just replaced the axios() function with cachify()
        
        handleResponse (response)
    } catch (error) {
        handleError (error)
    }
}

//handle api or cache response here
function handleResponse (response) {
    if (response.data) {
        //handle the response data
    }
    else {
        console.log(response)
    }
}

function handleError (error) {
    //handle if any error occurs during data refreshing on api call (ex: authentication error)
}

Notes

  • handleResponse: The function has been used as callback in postSync property and also been used to handle the response of api call.
  • handleError: The function has been used as errorCallback in cacheConfig and also been used to handle the error on api call.
  • Time specifier: CahcifyJS has 5 time specifiers s, m, h, d and w for seconds, minutes, hours, days and weeks respectively. If no specifier is provided, the value will be considered as milliseconds.

Configuration

When using CachifyJS, you can configure various options to customize the caching behavior. The cacheConfig object passed to the cachify function accepts the following properties:

  • key: (required) A string that uniquely identifies the API endpoint being called. This key is used as the key for caching the response in local storage. It's recommended to keep it similar to your api uri.

  • errorCallback: (required) A callback function that will be called if an error occurs during the API call. This can be used to handle errors such as authentication failures.

  • lifetime (optional): The amount of time in milliseconds that the cached response should be considered valid. After this time has elapsed, the cache will be invalidated. The default value is 7d or 1 week.

  • encryption (optional): For sensitive data, encryption can be enabled.

    • secretKey (required): To use encryption, you'll need to provide a secret key to the encryption configuration. This secret key will be used to encrypt and decrypt your data.
  • preSync: (optional) A boolean that simply enables caching after getting api response and then sending data to frontend.

  • postSync: (recommended) An object that defines how the cache should be updated after the API response is returned. This is useful when you want to keep the cache up to date with new data periodically.

    • callback: (required) A callback function that will be called with the cached data with a wrapper (ex: {data: cachedData}) after it has been cached.

    • skipApiCallFor: (optional) The amount of time to skip api call. If any api call is made too frequently and we want to reduce the call, we may use this configuration. Then any call to cachify() function with give data from cache without api call withing this time period.

    • syncTimeout: (optional) The amount of time to wait before syncing the cache with new data. This is useful if you want to avoid syncing the cache too frequently. It's a one time call.

    • syncInterval: (optional) The amount of time to wait before syncing the cache again. This is useful if you want to periodically update the cache with new data.

Scenarios

  1. Plain: CachifyJS will try to get data from cache. If data found, no api call will be made. Otherwise, it will make the api call, cache the data and return the cached data inside a wrapper. It's recommended to use lifetime for this case. After the cache being expired, new api call will be made to get fresh data. The cacheConfig should look like,

    const cacheConfig = {
        key: `product/list?status=active`,
        errorCallback: handleError,
        lifetime: '30m',
        encryption: {
            secretKey: 'my-secret-key'
        }
    }
  2. preSync: CachifyJS will make the api call, cache the response and return the response. The cacheConfig should look like,

    const cacheConfig = {
       key: `product/list?status=active`,
       errorCallback: handleError,
       preSync: true,
    }
  3. postSync: CachifyJS will try to get data from cache. If data not found, an immediate api call will be made. Otherwise, if syncTimeout is present in the config a single api call will be made according to the value.

    If syncInterval is present in the config, cachifyjs will make api call according to the syncInterval value and return the response.

    Data will be cached in both scenarios.

    If the api call is requested according to syncTimeout or syncInterval during skip timezone and cache data is present them the api call will simply be ignored and the cache data will be returned.

    const cacheConfig = {
        key: `product/list?status=active`,
        errorCallback: handleError,
        lifetime: '1h',
        postSync: {
           callback: handleResponse,
           skipApiCallFor: '10s',
           syncTimeout: 1,//default (ms)
           syncInterval: '3h',
        },
    }

    Notes:

    1. skipApiCallFor: The amount of time to skip api call.
    2. syncTimeout: The time delay after that api call will be made. It's a one time call.
    3. syncInterval: The time interval for the api call. It's a repetitive process. It works in background.

2. Set Cached Data:

The setCache function allows you to set new cached data in your frontend application. The data could be api response, any app state, you name it. With this new feature, you can easily set any data in the cache without depending on any type of network request or API call. To set cached data, import the setCache function into your JavaScript file and pass a config and data to the function. The function will set new data in cache.

Here's an example:

import {setCache} from "cachifyjs";

async function setWishListCache (data) {
    // configuration for updating
    const config = {
        key: `wishlist`,//Be sure to use unique key
        lifetime: '1h',
        encryption: {
            secretKey: 'my-secret-key'
        },
        after: {
           callback: handleResponse, 
        }
    }
        
    try {    
        await setCache(config, data);
    } catch (error) {
        console.log ("Set Cache Error:", error)
    }
}

function handleResponse (response) {
    //handle response after setting cached data
}

Configuration

When setting new data, the config object passed to the setCache function accepts the following properties:

  • key: (required) A string that uniquely identifies the cached data. This key is used as the key for caching the response in local storage.

  • lifetime (optional): The amount of time in milliseconds that the cached response should be considered valid. After this time has elapsed, the cache will be invalidated. The default value is 7d or 1 week.

  • encryption (optional): For sensitive data, encryption can be enabled.

    • secretKey (required): To use encryption, you'll need to provide a secret key to the encryption configuration. This secret key will be used to encrypt and decrypt your data.
  • after: (recommended) An object that defines the events after the data has been set. This is useful when you want create an effect after the setting up cached data.

    • callback: (required) A callback function that will be called with the cached data with a wrapper (ex: {data: cachedData}) after it has been cached.

3. Get Cached Data:

The getCache function allows you to get the cached data from your frontend application without complex configuration or subsequent api call.

Here's an example:

import {getCache} from "cachifyjs";

async function getWishListCache () {
    const config = {
        key: `wishlist`,    //it must be the same as the cached key
        encryption: {,      // if the cached data is ecrypted, the same encryption key is required.
            secretKey: 'my-secret-key'
        },
    }

    try {    
        const response = await getCache(config);
        handleResponse(response)
    } catch (error) {
        console.log ("Get Cache Error:", error)
    }
}

//handle cache response here
function handleResponse (response) {
    if (response.data) {
        //handle the response data
    }
    else {
        console.log(response)
    }
}

Notes

  • response: response is a wrapper around the cached data. Ex: {data: cachedData} or {message: "Data not found",nodata:true}.
  • handleResponse: The function has been used as callback in after property.

Configuration

When getting data, the config object passed to the getCache function accepts the following properties:

  • key: (required) This key identifies the cached data. It's mandatory to keep it same to the key of the cached data.

  • encryption (optional): If the cached data is encrypted then it's mandatory.

    • secretKey (required): To use encryption, you'll need to provide a secret key to the encryption configuration. This secret key will be used to decrypt your data.

4. Update Cached Data:

To update cached data, import the updateCache function into your JavaScript file and pass a config and data to the function. The function will update the cached data in frontend without making api call.

Here's an example:

import {updateCache} from "cachifyjs";

async function updateProductListCache (updatedData) {
    // configuration for updating
    const config = {
        key: `product/list?status=active`,//it must be the same as the cached key
        lifetime: '1h',
        encryption: {
            secretKey: 'my-secret-key'//it must be the same as the key used to cache the data
        },
        after: {
           callback: handleResponse, //the same callback previously use in cacheConfig
        }
    }
        
    try {    
        await updateCache(config, updatedData);
    } catch (error) {
        console.log ("Cache Update Error:", error)
    }
}

//the same function previously used to handle the api response
function handleResponse (response) {
    //handle api response here
}

Notes

  • handleResponse: The function has been used to handle the api response previously. This callback will be called after the data has been updated.

Configuration

When updating data, the config object passed to the updateCache function accepts the following properties:

  • key: (required) This key identifies the cached data and update it. It's mandatory to keep it similar to the key of the data needs to be updated.

  • lifetime (optional): The amount of time in milliseconds that the cached response should be considered valid. After this time has elapsed, the cache will be invalidated.

  • encryption (optional): For sensitive data, encryption can be enabled. If the cached data is encrypted then it's mandatory.

    • secretKey (required): To use encryption, you'll need to provide a secret key to the encryption configuration. This secret key will be used to encrypt and decrypt your data.
  • after: (recommended) An object that defines the events after the data has been updated. This is useful when you want create an effect after the update.

    • callback: (required) A callback function that will be called after the data has been updated. It should be the same method that was previously passed in cacheConfig during initial caching.

5. Remove Cached Data:

To remove cached data, import the removeCache function into your JavaScript file and pass a config with the key property to the function. The function will remove the cached data.

Here's an example:

import {removeCache} from "cachifyjs";

async function removeProductListCache () {
    const config = {
        key: `product/list?status=active`,//it must be the same as the cached key
    }

    try {    
        await removeCache(config);
    } catch (error) {
        console.log ("Cache Removal Error:", error)
    }
}

Change Log (v2.3)

  • Version 2.3.10 (2023-07-15)

  • Version 2.3.9 (2023-06-30)

    • Skip Api Call: The skip api call feature has been updated to check previous api call timestamp and determine the skip functionality.
  • Version 2.3.8 (2023-06-28)

    • Skip Api Call: The skipApiCallFor property inside postSync property of cacheConfig for function cachify() allows us to skip api calls. If any api call is made too frequently and we want to reduce the call, we may use this configuration.
  • Version 2.3.7 (2023-06-19)

    • Fixed the issue: Not calling api if data is cached even if postsync is enabled.

Dependencies

Axios, Crypto-JS

Conclusion

CachifyJS is a simple yet powerful tool that can help you optimize your frontend application's performance by reducing the number of API requests. By caching API responses in the browser's local storage, you can improve your application's response time and make it more responsive to user interactions. Give it a try in your next project!

Give Us Your Feedback