Installations

npm install v8-compile-cache-lib

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

17.3.1

NPM Version

6.14.15 Pull Requests

Open

0

Total

2

Closed

0

Merged

2

Issues

Open

3

Total

4

Closed

1

Releases

Unable to fetch releases

Languages

2

JavaScript

Shell

JavaScript (98.46%)

Shell (1.54%)

Developer

cspotcode

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

MIT License

13 Stars

111 Commits

1 Watchers

3 Branches

8 Contributors

Updated on Jul 08, 2025

Maintainers

1

View All 8 Contributors

Package Meta Information

Latest Version

3.0.1

Package Id

v8-compile-cache-lib@3.0.1

Unpacked Size

17.74 kB

Size

6.24 kB

File Count

6

NPM Version

6.14.15

Node Version

17.3.1

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

0%

NaN

Compared to previous day

Last Week

0%

NaN

Compared to previous week

Last Month

0%

NaN

Compared to previous month

Last Year

0%

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

9

babel-core eslint flow-parser rimraf rxjs semver tap temp yarn

v8-compile-cache-lib

Fork of v8-compile-cache exposed as an API for programmatic usage in other libraries and tools.

v8-compile-cache-lib attaches a require hook to use V8's code cache to speed up instantiation time. The "code cache" is the work of parsing and compiling done by V8.

The ability to tap into V8 to produce/consume this cache was introduced in Node v5.7.0.

Usage

Add the dependency:

1$ npm install --save v8-compile-cache-lib

Then, in your entry module add:

1require('v8-compile-cache-lib').install();

.install() in Node <5.7.0 is a noop – but you need at least Node 4.0.0 to support the ES2015 syntax used by v8-compile-cache-lib.

Options

Set the environment variable DISABLE_V8_COMPILE_CACHE=1 to disable the cache.

Cache directory is defined by environment variable V8_COMPILE_CACHE_CACHE_DIR or defaults to <os.tmpdir()>/v8-compile-cache-<V8_VERSION>.

Internals

Cache files are suffixed .BLOB and .MAP corresponding to the entry module that required v8-compile-cache-lib. The cache is entry module specific because it is faster to load the entire code cache into memory at once, than it is to read it from disk on a file-by-file basis.

Benchmarks

See https://github.com/cspotcode/v8-compile-cache-lib/tree/master/bench.

Load Times:

Module	Without Cache	With Cache
`babel-core`	`218ms`	`185ms`
`yarn`	`153ms`	`113ms`
`yarn` (bundled)	`228ms`	`105ms`

^ Includes the overhead of loading the cache itself.

Acknowledgements

The original v8-compile-cache from which this library is forked.
FileSystemBlobStore and NativeCompileCache are based on Atom's implementation of their v8 compile cache:
- https://github.com/atom/atom/blob/b0d7a8a/src/file-system-blob-store.js
- https://github.com/atom/atom/blob/b0d7a8a/src/native-compile-cache.js
mkdirpSync is based on:
- https://github.com/substack/node-mkdirp/blob/f2003bb/index.js#L55-L98

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.4

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More