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

@dependable/cache

v0.11.0

Published

A reactive cache for @dependable/state

Downloads

16

Readme

@dependable/cache

Checks Bundle Size

Reactive cache for storing entities using @dependable/state.

API documentation

Install

# npm
npm install --save @dependable/cache

# yarn
yarn add @dependable/cache

Usage

Create a cache

Let's create a cache for storing todo's.

import { Cache } from "@dependable/cache";
import { observable } from "@dependable/state";

const todos = new Cache("todos");

Loading state into the cache

Now we can load a todo into the cache using a resolver.

todos.load(42, async () => {
  const response = await fetch("https://example.com/todos/42");

  if (!response.ok) {
    throw new Error(response.statusText);
  }

  const data = await response.json();

  return {
    id: data.id,
    title: observable(data.title),
    completed: observable(data.completed),
  };
});

If you only would like to initialize a value, you can use the initialize method. It will only run the resolver if the value hasn't been initialized already.

todos.initialize(42, async () => {
  const response = await fetch("https://example.com/todos/42");

  if (!response.ok) {
    throw new Error(response.statusText);
  }

  const data = await response.json();

  return {
    id: data.id,
    title: observable(data.title),
    completed: observable(data.completed),
  };
});

Retrieving a value from the cache

We can get a value from the cache the following way.

import { UNINITIALIZED, LOADING, LOADED, FAILED } from "@dependable/cache";

const [todo, status, error] = todos.byId(42);

if (status === FAILED) {
  // Loading the todo failed.
  // If this was a reload, you will still have the old value.
  console.log(error);
} else if (status === LOADING) {
  // The todo is loading.
  // If this was a reload, you will still have the old value.
} else if (status === UNINITIALIZED) {
  // Loading the todo hasn't been started yet.
} else if (status === LOADED) {
  // The todo finished loading.
}

If the above call is done inside of a @dependable/state computed or a @dependable/view component, it will update every time the status changes.

Getting only the status

If you just need the status of a cache entry, you can use the statusById method.

import { UNINITIALIZED, LOADING, LOADED, FAILED } from "@dependable/cache";

const status = todos.statusById(42);

if (status === FAILED) {
  // Loading the todo failed.
  // If this was a reload, you will still have the old value.
  console.log(error);
} else if (status === LOADING) {
  // The todo is loading.
} else if (status === UNINITIALIZED) {
  // Loading the todo hasn't been started yet.
} else if (status === LOADED) {
  // The todo finished loading.
}

Evicting values

You can evict the a value the following way that will turn it back to be uninitialized.

todos.evict(42);

const [todo, status, error] = todos.byId(42);

// will have null for the todo and a status of UNINITIALIZED.

You can also clear the entire cache with the clear method.

Storing non-serializable objects

In case you need to store non-serializable objects in a cache, you can create a cache without giving it a name. This way the observable backing the cache will be anonymous and it's values will not be handled by the development tools.

This is useful for lazy loading components.

const components = new Cache();

components.load("editor", import("./editor.js"));

const [module, status, error] = components.byId("editor");