Are your build scripts slow? The cached-build-function package can help. It makes it easy to write build functions that use a cache folder on the file system to only recompute their output in case their input has changed.

How it works:

• Results (values or errors) are stored as JSON in the cache folder
• Function arguments are used as cache keys (i.e. their hashed JSON value)
• Cache entries can be defined to be valid only as long as certain files haven't changed
• Files and folders can also be stored inside the cache
• Cleanup mechanism to remove old cache entries
• Queue mode: Schedule multiple function calls and execute them in one go to see how many calls have a cache hit in advance.

You can create your CachedBuildFunction by inheriting from the class:

const { readFile } = require('fs-extra')
const CachedBuildFunction = require('cached-build-function')

class ProcessFile extends CachedBuildFunction {
  static get version () { return 1 }

  static async run (srcPath) {
   const srcBuffer = await readFile(this.observe(srcPath))
   return someExpensiveOperation(srcBuffer.toString())
  }
}

To use it, create an instance and call it like a function:

Note: Yes, instances of JavaScript classes can be functions :)

const processFile = new ProcessFile({ cachePath: 'path/to/my/cache') })

await processFile('data1.json') // Cheap if files havn't changed
await processFile('data2.json')

await myResize.cleanUnused() // Removes unused cache entries

Here are some more complex examples:

• Excel file reading example: Short and easy to understand example
• Image resizing example: Uses cacheKey(), after(), cache files and "queue mode"

• cached-build-function
  • CachedBuildFunction ⏏
    • new CachedBuildFunction(options)
    • instance
      • .queuedCount ⇒ number
      • .enqueue(...args) ⇒ Promise
      • .flush(options) ⇒ Promise
      • .clearQueue()
      • .cleanUnused() ⇒ Promise
    • static
      • .version ⇒ string | number
      • .outputConsistency ⇒ boolean
      • .run() ⇒ Promise
      • .after() ⇒ Promise
      • .cacheKey() ⇒ *

The CachedBuildFunction class is abstract. To use it, you need to create a subclass and implement the static properties version and run.

class MyBuildFn extends CachedBuildFunction {
  static get version () { return 123 }
  static async run (...) { ... }
}

Next, you can create an instance with the new operator and because instances are functions you can call it.

const myBuildFn = new MyBuildFn({ cachePath: '...' })
const output = await myBuildFn(arg1, arg2, ...)

CachedBuildFunction instances are asynchronouse functions. This means that they return a promise. The promise settles after the result could either be fetched from the cache or has been calculated by the run() function.

For consistency, the value or reason to which the promise settles always looks like it comes from the cache, i.e. values are deserialized from JSON even they were just created by the run() function.

Furthermore, the returned promise has some extra properties:

• eventEmitter EventEmitter that fires the following events:
  • 'checkedCache': Fired after the cache check has completed. Its data is an object with a cacheHit boolean property
  • 'cacheHit': Fired in case of a cache hit
  • 'cacheMiss': Fired in case of a cache miss
• on(): Calls eventEmitter.on() and is chainable. This means you can do this:

  const output = await myBuildFn()
    .on('cacheHit', () => { console.log('Wohoo! Cache hit') })

Kind: Exported class

Number of queued operations

Kind: instance property of CachedBuildFunction

This function lets you enqueue a function call. Only the cache check will be performed immediately asynchronously, the call to run() (if needed) is delayed until you call flush().

Kind: instance method of CachedBuildFunction Returns: Promise - Same promise as if you call the CachedBuildFunction

This function lets you flush the queue.

Kind: instance method of CachedBuildFunction Returns: Promise - Promise with some extra properties:

• eventEmitter EventEmitter that fires the following event:
  • 'checkedCache': Fired after the cache checks have completed. Its data is an object with the properties:
    • count: Total number of items
    • cacheHitCount: Number of items that had a cache hit
    • cacheMissCount: Number of items that had a cache miss
• on(): Calls eventEmitter.on() and is chainable. This means you can do this:

  await myFn.flush()
    .on('checkedCache', ({ cacheHitCount, cacheMissCount }) => {
       console.log(`Found ${cacheHitCount} items in the cache, ` +
                   `need to compute ${cacheHitCount} items`)
    })

Clears the queue

Kind: instance method of CachedBuildFunction

The CachedBuildFunction internally keeps track of which cache entries have been accessed since it was created. The cleanUnused() function removes any cache entries on disk that haven't been accessed.

Kind: instance method of CachedBuildFunction

The static version property returns an integer or string that reflects the current version of your run() function. You should change this property whenever you make behavioral changes to the function. This ensures that previously created cache entries, which are now outdated, are not used to produce the output. You can set the version to Math.random() if you want to temporarily disable caching during development.

Kind: static abstract property of CachedBuildFunction

The static outputConsistency property is intended for advanced users only. Normally the output value is always deserialized from JSON to make the output look like it comes from the cache whether or not it actually did. Setting this property to false disables this deserialization which is not striclty necessary for output values that were just created by executing run(). You should either always leave this option set to true or at least during development. The performance gain is relatively minimal if you're using your CachedBuildFunction to perform appropriately expensive operations because deserialization from JSON is cheap compared to operations like hashing large files, resizing images, reading excel files etc. If you set this property to false, you can run into problems where your output looks different depending on whether it came from the cache. To prevent bugs in your code, it is recommended to leave it to true.

Kind: static property of CachedBuildFunction Default: true

The static run() method is used to produce the output whenever no valid cache entry can be found. It is called with the arguments that the CachedBuildFunction was called with. The return value of this function must be serializable (and deserializable) to (and from) JSON because it is written to the cache on disk. If the function throws an error during execution, the error will also be serialized and cached. The this inside the function is special and has the following methods:

• this.observe(path): You should call this function on any file paths that you're reading from. This ensures that the cached output is only valid as long as none of the observed files have changed. Whenever a cache entry is found, CachedBuildFunction checks whether all observed files remain unchanged before it decides to use the cache entry. It does so by comparing the file size and creation and modification timestamps. For convenience, observe() returns its input. It won't throw an error if it can't find the file.
• this.cachePath(name): Returns a path inside the cache folder. You can use this path to create a file or folder that you want to cache. Later inside the after() function, you can access the stored file or folder. The name parameter has to be a string that is valid inside file names. The returned path has the form `${cacheFolder}/${cacheKey}-${name}`.

Kind: static abstract method of CachedBuildFunction

The static after() method can be used to transform the output produced by run() (given that no error occured). Just like run(), it is called with the arguments that the CachedBuildFunction was called with. Its return value becomes the return value of the CachedBuildFunction. This means that you can use it to transform the output which had to be stored as JSON when it was cached into something else. Or, you can use it to copy files from the cache to their final destinations. The this inside the function has the following properties and methods:

• this.value: The value from the cache produced by the run() function
• this.cachePath(name): Same as cachePath() inside the run() function. You can use it to read or copy the file or folder stored at the path in the cache. It is important that you do not modify the file or folder because it has to be there exactly the same the next time the CachedBuildFunction is called with the same input.

Kind: static method of CachedBuildFunction

The cacheKey static method selects the arguments that determine the cache key. The cache key will be created by serializing the return value to JSON and then hashing it. You should override this function if:

• you have parameters that cannot be serialized to JSON and you want to transform them into something that can.
• you have parameters that do not influence the behavior of the run() function, e.g. a parameter that is only used in the after() function.

Kind: static method of CachedBuildFunction