file-entry-cache
npmv11.1.5TypeScriptA lightweight cache for file metadata, ideal for processes that work on a specific set of files and only need to reprocess files that have changed since the last run
Safe to adopt
Yes — file-entry-cache scores well across adoption, maintenance, weight, supply chain, and licensing. 134.5M downloads per week and 1 known dependents. Last published 74 days ago. 24 releases in the last 2 years.
- AAdoption: grade A, Excellent.
134.5M downloads per week and 1 known dependents.
- AMaintenance: grade A, Excellent.
Last published 74 days ago. 24 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 87 KB installed (at least — some of the tree is still being crawled).
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding file-entry-cache to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the file-entry-cache README.
import fileEntryCache from 'file-entry-cache';
const cache = fileEntryCache.create('cache1');
// Using relative paths
let fileDescriptor = cache.getFileDescriptor('./src/file.txt');
console.log(fileDescriptor.changed); // true as it is the first time
console.log(fileDescriptor.key); // './src/file.txt' (stored as provided)
// Repeated calls keep reporting `changed: true` until you persist the state
// with reconcile(); only then does the file become the cached baseline.
cache.reconcile();
fileDescriptor = cache.getFileDescriptor('./src/file.txt');
console.log(fileDescriptor.changed); // false as it has not changed since reconcile()file-entry-cache vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| file-entry-cachethis page | 134.5M | 1 | MIT | 2 months ago |
| memoize-one | 32.7M | 3 | MIT | 1 day ago |
| make-fetch-happen | 22.8M | 1 | ISC | 1 day ago |
| env-paths | 0 | 2 | MIT | 1 day ago |
| define-lazy-prop | 0 | 1 | MIT | 1 day ago |
| nocache | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by file-entry-cache v11.1.5. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (3)
Used by
Popular packages that depend on file-entry-cache.
Relationship graph
Dependencies (left) and dependents (right) of file-entry-cache.
Frequently installed together
Runtime typescript and ESM support for Node.js
Constants and utilities about visitor keys to traverse AST.
Escape RegExp special characters
TypeScript definitions for estree
An AST-based pattern checker for JavaScript.
Returns `true` if the given string looks like a glob pattern or an extglob pattern. This makes it easy to create code that only uses external modules like node-glob when necessary, resulting in much faster code execution and initialization time, and a bet
Prettier is an opinionated code formatter
Helper utilities for creating ESLint configuration
ECMAScript parsing infrastructure for multipurpose analysis
deterministic JSON.stringify() with custom sorting to get deterministic hashes from stringified results, with no public domain dependencies
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
The fast, flexible & elegant library for parsing and manipulating HTML and XML.
Release history
19 releases in the last two years, typically about 32 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 11.1.5latest | 2 months ago | 87 KB | MIT |
| 11.1.3 | 4 months ago | 85 KB | MIT |
| 11.1.2 | 7 months ago | 85 KB | MIT |
| 11.1.1 | 9 months ago | 85 KB | MIT |
| 11.1.0 | 11 months ago | 64 KB | MIT |
| 11.0.0 | 11 months ago | 63 KB | MIT |
| 11.0.0-beta.5 | 11 months ago | 59 KB | MIT |
| 11.0.0-beta.4 | 11 months ago | 57 KB | MIT |
| 11.0.0-beta.3 | 11 months ago | 68 KB | MIT |
| 11.0.0-beta.2 | 11 months ago | 70 KB | MIT |
| 11.0.0-beta.1 | 11 months ago | 50 KB | MIT |
| 10.1.4 | 1 year ago | 55 KB | MIT |
| 10.1.3 | 1 year ago | 55 KB | MIT |
| 10.1.1 | 1 year ago | 55 KB | MIT |
| 10.1.0 | 1 year ago | 55 KB | MIT |
Overview
file-entry-cache is an npm package that a lightweight cache for file metadata, ideal for processes that work on a specific set of files and only need to reprocess files that have changed since the last run. It is extremely widely used, with about 134.5M downloads per week and 1 known dependents in the graph. The latest version is 11.1.5, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a lightweight cache for file metadata, ideal for processes that work on a specific set of files and only need to reprocess files that have changed since the last run and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (134.5M weekly downloads).
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use file-entry-cache?
Yes — file-entry-cache scores well across adoption, maintenance, weight, supply chain, and licensing. 134.5M downloads per week and 1 known dependents. Last published 74 days ago. 24 releases in the last 2 years.
How do I install file-entry-cache?
Run `npm install file-entry-cache` to add file-entry-cache to your npm project.
How many dependencies does file-entry-cache have?
file-entry-cache declares 4 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 87 KB on disk.
What license is file-entry-cache released under?
file-entry-cache is distributed under the MIT license.
How popular is file-entry-cache?
file-entry-cache has approximately 134,452,990 downloads per week and 1 known dependent packages.
Is file-entry-cache still maintained?
The most recent release of file-entry-cache (v11.1.5) was published 2 months ago.
Does file-entry-cache run install scripts?
No. file-entry-cache does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.