test-exclude
npmv8.0.0test for inclusion or exclusion of paths using globs
Safe to adopt
Yes — test-exclude scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 199 days ago. 2 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 199 days ago. 2 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 8 transitive packages, about 2.7 MB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 3 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
ISC — 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 test-exclude 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.
Licenses in the dependency tree
Every license you inherit by installing test-exclude, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node 20 || >=22
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the test-exclude README.
const TestExclude = require('test-exclude');
const exclude = new TestExclude();
if (exclude().shouldInstrument('./foo.js')) {
// let's instrument this file for test coverage!
}test-exclude 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 |
|---|---|---|---|---|
| test-excludethis page | 0 | 1 | ISC | 6 months ago |
| filter-obj | 15.8M | 1 | MIT | 1 day ago |
| is-glob | 137.4M | 3 | MIT | 1 day ago |
| fast-glob | 135.1M | 8 | MIT | 1 day ago |
| cosmiconfig | 115.3M | 3 | MIT | 1 day ago |
| totalist | 30M | 1 | MIT | 1 day ago |
Dependencies
Declared by test-exclude v8.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on test-exclude.
Relationship graph
Dependencies (left) and dependents (right) of test-exclude.
Frequently installed together
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
Schemas describing various structures used by nyc and istanbuljs
Core istanbul API for JS code coverage
General utilities for plugins to use
Utility function to load nyc configuration
Compile ES2015 block scoping (const and let) to ES5
This plugin transforms ES2015 modules to CommonJS
Release history
2 releases in the last two years, typically about 32 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 8.0.0latest | 6 months ago | 11 KB | ISC |
| 7.0.2 | 6 months ago | 11 KB | ISC |
| 7.0.1 | 2 years ago | 11 KB | ISC |
| 7.0.0 | 2 years ago | 11 KB | ISC |
| 6.0.0 | 6 years ago | 23 KB | ISC |
| 6.0.0-alpha.3 | 6 years ago | 23 KB | ISC |
| 6.0.0-alhpa.3 | 6 years ago | 23 KB | ISC |
| 6.0.0-alpha.2 | 6 years ago | 22 KB | ISC |
| 6.0.0-alpha.1 | 7 years ago | 19 KB | ISC |
| 6.0.0-alpha.0 | 7 years ago | 18 KB | ISC |
| 5.2.3 | 7 years ago | 17 KB | ISC |
| 5.2.2 | 7 years ago | 17 KB | ISC |
| 5.2.1 | 7 years ago | 17 KB | ISC |
| 5.2.0 | 7 years ago | 17 KB | ISC |
| 5.1.0 | 7 years ago | 15 KB | ISC |
Overview
test-exclude is an npm package that test for inclusion or exclusion of paths using globs. It has 1 known dependents in the graph. The latest version is 8.0.0, released under the ISC license.
Who should use it
Teams working in the npm ecosystem who need test for inclusion or exclusion of paths using globs and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (ISC).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use test-exclude?
Yes — test-exclude scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 199 days ago. 2 releases in the last 2 years.
How do I install test-exclude?
Run `npm install test-exclude` to add test-exclude to your npm project.
How many dependencies does test-exclude have?
test-exclude declares 5 direct dependencies and pulls in 8 packages in total once its runtime tree is resolved totalling about 2.7 MB on disk.
What license is test-exclude released under?
test-exclude is distributed under the ISC license. Its dependency tree also includes: BlueOak-1.0.0, MIT.
How popular is test-exclude?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on test-exclude.
Is test-exclude still maintained?
The most recent release of test-exclude (v8.0.0) was published 6 months ago.
Does test-exclude run install scripts?
No. test-exclude does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.