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

@bit/loader-cache

v2.0.0

Published

Cache plugin for bit-loader

Downloads

18

Readme

bit-loader-cache

Greenkeeper badge

Caching plugin for bit-loader. This helps increase build times after initial build.

compatible with:

options and usage

const Bitbundler = require("@bit/bundler");

const bitbundler = new Bitbundler({
  watch: true,
  loader: [
    "@bit/loader-cache"
  ]
})

timeout

Write operations are throttled to prevent nasty issues with performance, and you can control how frequently write operations are retried (in milliseconds). Default value is 3000 milliseconds, which is 3 seconds.

cachePlugin({
  timeout: 1000
})

dest

File name to write the cache to. Defaults to .bundler-cache.json and written to the current working directory.

cachePlugin({
  dest: "cache.json"
})

connector

The cache plugin has the concept of connectors, which is basically a small interface you can implement for writing custom data sources.

The interface for a connector is relatively trivial and they are Promise compatible.

  • set, which takes in an id and a payload to store.
  • get, which takes the id from a set operation.
  • flush which is called whenever changes should be flushed.

You can take a look at the default connector, which basically just writes to the local disk.

Other connectors included are:

Examples

Elasticsearch

const Bitbundler = require("@bit/bundler");
const esConnector = require("@bit/loader-cache/connectors/elasticsearch");

const bitbundler = new Bitbundler({
  loader: [
    [ "@bit/loader-cache", {
      connector: esConnector({
        host: "localhost:9200",
        index: "cache_example",
        type: "modules"
      })
    })
  ]
});

bitbundler.bundle({
  src: "src/main.js",
  dest: "dest/cache_plugin.js"
});

Redis

The redis connector takes an optional flag watch that when set to true will keep the redis connector connected until the process is stopped. Otherwise, the redis connector exits when all the data is flushed.

const Bitbundler = require("@bit/bundler");
const redisConnector = require("@bit/loader-cache/connectors/redis");

const bitbundler = new Bitbundler({
  loader: [
    [ "@bit/loader-cache", {
      connector: redisConnector()
    }]
  ]
});

bitbundler.bundle({
  src: "src/main.js",
  dest: "dest/cache_plugin.js"
});

Docker

docker-compose

There are a couple of docker-compose files for spinning up elasticsearch and redis environments. You can run whichever you want to work with.

Elasticsearch

To spin up elasticsearch as well as kibana for a UI to run queries on elasticsearch (and more), you can use the es-docker-compose.yml configuration file.

$ docker-compose -f es-docker-compose.yml up

You can go to http://localhost:5601 in order to access kibana in the browser to see the data stored in elasticsearch.

Redis

To spin up a redis environment you can use the redis-docker-compose.yaml configuration file.

$ docker-compose -f redis-docker-compose.yml up