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

filru

v2.1.0

Published

least-recently-used cache for files on disk

Downloads

26

Readme

filru    Build Status

A pure-disk based least-recently-used (LRU) cache.

Nothing is kept in memory. This has the benefit of persisting across application restarts, and not taking up any RAM.

The cache is constrained by size (bytes), and optionally by file age.

Use Cases

filru is much slower than an in-memory cache, so use cases are:

  • a simplistic caching layer for frequent HTTP requests, since OS file system caching is much faster than doing a network request
  • caching the results of CPU-intensive operations
  • caching slow operations across multiple network requests
  • caching large items

Usage

Node.js >= version 6

npm install filru
const Filru = require('filru');
const require('request-promise-native'); // optional for loading async when not in cache
const handleErr = (err) => {
  throw err;
};

const maxBytes = 50 * 1024 * 1024; // 50 megabytes
const maxAge = 24 * 60 * 60 * 1000; // 1 day
const hashSeed = 'cache4gold'; // optional, random seed string
const pruneInterval = 1000 * 60 * 60; // optional, defaults to 1 hour
const f = new Filru({ dir: '/tmp/filru', maxBytes, maxAge, hashSeed, pruneInterval });

// optionally add a load function for when an object
// is not found in the cache
f.load = function customLoad(key) {
  // Custom async load function must return a promise.
  return request.get('https://my-site.com/' + key);
};

f.start()
  .then(() => {
    // fill the cache
    f.set('jimmy.txt', 'yo').catch(handleErr);
    f.get('jimmy.txt')
        .then((buffer) => {
          console.log('got jimmy:', buffer.toString('utf8')); // "yo"
        })
        .catch(handleErr);
    // stop cleanup job
    f.stop();
  })
  .catch(err => {
    throw err;
  });

Tests

npm test

Debugging

Run your application with DEBUG=filru*

License

MIT

See LICENSE file in the root of this directory.