Package Exports
- caching-transform
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (caching-transform) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
caching-transform

Wraps a transform and provides caching.
Caching transform results can greatly improve performance. nyc
saw dramatic performance increases when we implemented caching.
Install
$ npm install --save caching-transform
Usage
const cachingTransform = require('caching-transform');
cachingTransform({
cacheDir: '/path/to/cache/directory',
salt: 'hash-salt',
transform: (input, additionalData, hash) => {
// ...
return transformedResult;
}
});
API
cachingTransform(options)
Returns a transform callback that takes two arguments:
input
a string to be transformedadditionalData
an arbitrary data object.
Both arguments are passed to the wrapped transform. Results are cached in the cache directory using an md5
hash of input
and an optional salt
value. If a cache entry already exist for input
, the wrapped transform function will never be called.
options
salt
Type: string
Default: empty string
A string that uniquely identifies your transform, a typical salt value might be the concatenation of the module name of your transform and its version':
const pkg = require('my-transform/package.json');
const salt = pkg.name + ':' + pkg.version;
Including the package version in the salt ensures existing cache entries will be automatically invalidated when you bump the version of your transform. If your transform relies on additional dependencies, and the transform output might change as those dependencies update, then your salt should incorporate the versions of those dependencies as well.
transform
Type: Function(input: string, additionalData: *, hash: string): string
input
: The string to be transformed. passed through from the wrapper.additionalData
: An arbitrary data object passed through from the wrapper. A typical value might be a string filename.hash
: The salted hash ofinput
. Useful if you intend to create additional cache entries beyond the transform result (i.e.nyc
also creates cache entries for source-map data). This value is not available if the cache is disabled, if you still need it, it can be computed viacachingTransform.getHash(input, salt)
.
The transform function should return a string
containing the result of transforming input
.
factory
Type: Function(cacheDir: string): transformFunction
If the transform
function is expensive to create, and it is reasonable to expect that it may never be called during the life of the process, you may supply a factory
function that will be used to create the transform
function the first time it is needed.
cacheDir
Type: string
The directory where cached transform results will be stored. The directory is automatically created with mkdirp
. You can set options.createCacheDir = false
if you are certain the directory already exists.
ext
Type: string
Default: empty string
An extension that will be appended to the salted hash to create the filename inside your cache directory. It is not required, but recommended if you know the file type. Appending the extension allows you to easily inspect the contents of the cache directory with your file browser.
shouldTransform
Type: Function(input: string, additonalData: *)
Default: always transform
A function that examines input
and additionalData
to determine whether the transform should be applied. Returning false
means the transform will not be applied and input
will be returned unmodified.
disableCache
Type: boolean
Default: false
If true
, the cache is ignored and the transform is used every time regardless of cache contents.
License
MIT © James Talmage