Home / npm packages / file-entry-cache

file-entry-cache source code

Every file of file-entry-cache@11.1.5 as published on npm: 7 files, 89 KB. Search them by exact text or regex, in milliseconds.

It uses: process.env, the fs module, crypto.

What file-entry-cache uses

APIIn file-entry-cache
eval()
runs a string as JavaScript
NoWho does
new Function()
builds a function from a string, like eval (with or without new)
NoWho does
child_process
starts other programs
NoWho does
process.env
reads environment variables
Yes: 1 file
e.g. README.md
See the lines
the fs module
reads and writes files
Yes: 2 files
e.g. dist/index.cjs
See the lines
http / https
makes or serves HTTP requests with Node's own modules
NoWho does
fetch()
makes HTTP requests
NoWho does
XMLHttpRequest
makes HTTP requests the old browser way
NoWho does
crypto
hashes, encrypts or makes random numbers
Yes: 2 files
e.g. dist/index.cjs
See the lines
WebAssembly
loads WebAssembly code
NoWho does
document.cookie
reads or writes browser cookies
NoWho does
install scripts
runs a script when it's installed
NoWho does

Exact matches in the published files, so a mention in a comment counts too: open the lines to check.

Largest files

FileSize
README.md28 KB
dist/index.cjs18 KB
dist/index.mjs17 KB
dist/index.d.cts12 KB
dist/index.d.mts12 KB
package.json1.5 KB
LICENSE1.1 KB

Questions

How many files are in file-entry-cache?

Version 11.1.5 of file-entry-cache publishes 7 files of source, 89 KB in all, not counting images, fonts and source maps.

Does file-entry-cache use eval?

No: file-entry-cache doesn't call eval() anywhere in its published files.

Does file-entry-cache start other programs?

No: file-entry-cache doesn't use child_process anywhere in its published files.

Does file-entry-cache run an install script?

No: file-entry-cache has no preinstall, install or postinstall script in its package.json.

npm packages that use…

Every package we've indexed →

Search your own code like this

The same engine answers over your documents and repositories: exact text and regex, every match counted, from your code or your AI agent.

See StackGrep Engine