</>PackageGraphPackageGraph

nocache

npmv4.0.0TypeScript

Middleware to destroy caching

Not recommended for new projects

No — nocache should not be adopted for new projects. Last published 1196 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1196 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 3.1 KB installed.

  • 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 nocache to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

3.1 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >=16.0.0
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the nocache README.

javascriptFull README ↗
const nocache = require("nocache");

// ...

app.use(nocache());

nocache vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
nocachethis page01MIT3 years ago
cors69.7M6MIT1 day ago
make-fetch-happen22.8M1ISC1 day ago
cacache01ISC1 day ago
file-entry-cache134.5M1MIT1 day ago
express92.8M17MIT1 day ago

Dependencies

Declared by nocache v4.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on nocache.

Relationship graph

Dependencies (left) and dependents (right) of nocache.

@react-native-com…nocache
nocache dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 124 days apart.

Recent versions of nocache
VersionPublishedSizeLicense
4.0.0latest3 years ago3.1 KBMIT
3.0.44 years ago3.2 KBMIT
3.0.34 years ago4.2 KBMIT
3.0.24 years ago4.0 KBMIT
3.0.15 years ago4.5 KBMIT
3.0.05 years ago4.4 KBMIT
2.1.07 years ago4.4 KBMIT
2.0.010 years agoMIT
1.0.110 years agoMIT
1.0.010 years agoMIT
0.4.011 years agoMIT
0.3.011 years agoMIT
0.2.011 years agoMIT
0.1.012 years agoMIT

Overview

nocache is an npm package that middleware to destroy caching. It has 1 known dependents in the graph. The latest version is 4.0.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need middleware to destroy caching and value a focused 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

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).
  • Lean dependency tree (2 direct dependencies).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use nocache?

No — nocache should not be adopted for new projects. Last published 1196 days ago.

How do I install nocache?

Run `npm install nocache` to add nocache to your npm project.

What license is nocache released under?

nocache is distributed under the MIT license.

How popular is nocache?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on nocache.

Is nocache still maintained?

The most recent release of nocache (v4.0.0) was published 3 years ago.

Does nocache run install scripts?

No. nocache does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.