gaze
npmv1.1.3A globbing fs.watch wrapper built from the best parts of other fine watch libs.
Not recommended for new projects
No — gaze should not be adopted for new projects. Last published 3033 days ago.
- AAdoption: grade A, Excellent.
2M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 3033 days ago.
- BWeight: grade B, Good.
Pulls in 9 transitive packages, about 4.0 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.
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 gaze 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 gaze, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 4.0.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the gaze README.
var gaze = require('gaze');
// Watch all .js files/dirs in process.cwd()
gaze('**/*.js', function(err, watcher) {
// Files have all started watching
// watcher === this
// Get all watched files
var watched = this.watched();
// On file changed
this.on('changed', function(filepath) {
console.log(filepath + ' was changed');
});gaze 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 |
|---|---|---|---|---|
| gazethis page | 2M | 1 | MIT | 8 years ago |
| fb-watchman | 0 | 3 | Apache-2.0 | 1 day ago |
| is-glob | 137.4M | 3 | MIT | 1 day ago |
| fast-glob | 135.1M | 8 | MIT | 1 day ago |
| jest | 42.1M | 70 | MIT | 1 day ago |
| totalist | 30M | 1 | MIT | 1 day ago |
Dependencies
Declared by gaze v1.1.3. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (8)
Used by
Popular packages that depend on gaze.
Relationship graph
Dependencies (left) and dependents (right) of gaze.
Frequently installed together
Lodash modular utilities.
An AST-based pattern checker for JavaScript.
CLI app helper
Opinionated, caching, retrying fetch client
An optionally-asynchronous forEach with an interesting interface.
Given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem.
Non-blocking stdout stream
Cross platform child_process#spawn and child_process#spawnSync
the most correct and second fastest glob implementation in JavaScript
Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility
Parse sass files and extract a graph of imports
Release history
No releases in the last two years, typically about 49 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.1.3latest | 8 years ago | 25 KB | MIT |
| 1.1.2 | 10 years ago | — | MIT |
| 1.1.1 | 10 years ago | — | MIT |
| 1.1.0 | 10 years ago | — | MIT |
| 1.0.0 | 10 years ago | — | MIT |
| 0.5.2 | 11 years ago | — | MIT |
| 0.6.4 | 12 years ago | — | MIT |
| 0.6.3 | 12 years ago | — | MIT |
| 0.6.2 | 12 years ago | — | MIT |
| 0.6.1 | 12 years ago | — | MIT |
| 0.6.0 | 12 years ago | — | MIT |
| 0.5.1 | 12 years ago | — | MIT |
| 0.5.0 | 12 years ago | — | MIT |
| 0.4.3 | 13 years ago | — | MIT |
| 0.4.2 | 13 years ago | — | MIT |
Overview
gaze is an npm package that a globbing fs.watch wrapper built from the best parts of other fine watch libs. It is very popular, with about 2M downloads per week and 1 known dependents in the graph. The latest version is 1.1.3, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a globbing fs.watch wrapper built from the best parts of other fine watch libs and value a battle-tested, widely-adopted 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
- Large, well-established user base (2M weekly downloads).
- Clear open-source license (MIT).
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 gaze?
No — gaze should not be adopted for new projects. Last published 3033 days ago.
How do I install gaze?
Run `npm install gaze` to add gaze to your npm project.
How many dependencies does gaze have?
gaze declares 9 direct dependencies and pulls in 9 packages in total once its runtime tree is resolved totalling about 4.0 MB on disk.
What license is gaze released under?
gaze is distributed under the MIT license. Its dependency tree also includes: BlueOak-1.0.0, MIT.
How popular is gaze?
gaze has approximately 2,016,263 downloads per week and 1 known dependent packages.
Is gaze still maintained?
The most recent release of gaze (v1.1.3) was published 8 years ago.
Does gaze run install scripts?
No. gaze does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.