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

solid-cache

v0.2.1

Published

Cached data-fetching for SolidJS

Downloads

28

Readme

solid-cache

Cache boundaries and resource caching in SolidJS

NPM JavaScript Style GuideOpen in CodeSandbox

Install

npm i solid-cache
yarn add solid-cache
pnpm add solid-cache

Usage

<CacheBoundary>

<CacheBoundary> creates a contextual cache for all the cached resources to read/write resource results.

import { CacheBoundary } from 'solid-cache';

export default function App() {
  return (
    <CacheBoundary>
      <Main />
    </CacheBoundary>
  );
}

It's ideal to add a <CacheBoundary> at the root of your application, but you can also do it granularly such that different parts of the application don't have to share the same cache.

<>
  <CacheBoundary>
    <Navigation />
  </CacheBoundary>
  <CacheBoundary>
    <PageContent />
  </CacheBoundary>
</>

createCachedResource

A primitive similar to createResource, except createCachedResource works differently.

For createCacheResource to be "cached", it requires a <CacheBoundary> as an ancestor component, and it needs a "key" so it knows where to access or share its cached data.

createCachedResource also returns data and isFetching: data is a Resource while isFetching is a reactive boolean signal.

import { createCachedResource } from 'solid-cache';

function Profile() {
  const { data, isFetching } = createCachedResource({
    key: '/profile',
    get: () => getUserProfile(),
  });

  return (
    <div
      style={{
        opacity: isFetching() ? 0.5 : 1,
      }}
    >
      <Suspense fallback={<ProfileSkeleton />}>
        <ProfileDetails data={data()?.details} />
        <ProfileTimeline data={data()?.posts} />
      </Suspense>
    </div>
  );
}

createCachedResource can also accept a source like createResource however it won't refetch if the key remains unchanged.

const { data, isFetching } = createCachedResource({
  source: () => id(),
  key: (currentId) => `/user/${currentId}`,
  get: (currentID) => getUser(currentId),
});

If there are multiple createCachedResource instances that share the same key, only one is going to fetch and the rest will re-use the same cached value as the fetching instance.

useCacheBoundaryRefresh

useCacheBoundaryRefresh returns a function that makes all createCachedResource instances to simultaneously refresh in the same <CacheBoundary>.

function RefreshUser() {
  const refresh = useCacheBoundaryRefresh();

  return <RefreshButton onClick={() => refresh()} />
}

However, if you want to "refresh in the background" while keeping the old data, you can call refresh(true) instead, this way, the UI doesn't need to show a loading UI.

fetch

A wrapper for createCachedResource and the native fetch API.

import { fetch } from 'solid-cache';

function DogImage() {
  const { data, isFetching } = fetch('https://dog.ceo/api/breed/shiba/images/random').json();

  return (
    <Suspense>
      <img
        src={data()?.message}
        style={{ opacity: isFetching() ? 0.5 : 1 }}
      />
    </Suspense>
  );
}

Sponsors

Sponsors

License

MIT © lxsmnsyc