walker
npmv1.0.8A simple directory tree walker.
Not recommended for new projects
No — walker should not be adopted for new projects. Last published 1782 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1782 days ago.
- AWeight: grade A, Excellent.
Pulls in 2 transitive packages, about 14 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
Apache-2.0 — 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 walker 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.
Licenses in the dependency tree
Every license you inherit by installing walker, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the walker README.
Walker('/etc/')
.filterDir(function(dir, stat) {
if (dir === '/etc/pam.d') {
console.warn('Skipping /etc/pam.d and children')
return false
}
return true
})
.on('entry', function(entry, stat) {
console.log('Got entry: ' + entry)
})
.on('dir', function(dir, stat) {
console.log('Got directory: ' + dir)
})walker 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 |
|---|---|---|---|---|
| walkerthis page | 0 | 3 | Apache-2.0 | 4 years ago |
| @humanfs/core | 0 | 1 | Apache-2.0 | 1 day ago |
| @humanfs/types | 0 | 2 | Apache-2.0 | 1 day ago |
| @humanfs/node | 0 | 1 | Apache-2.0 | 1 day ago |
| make-dir | 0 | 2 | MIT | 1 day ago |
| normalize-path | 72.6M | 1 | MIT | 1 day ago |
Dependencies
Declared by walker v1.0.8. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (1)
Used by
Popular packages that depend on walker.
`jest-haste-map` is a module used by Jest, a popular JavaScript testing framework, to create a fast lookup of files in a project. It helps Jest efficiently locate and track changes in files during testing, making it particularly useful for large projects
A metro-file-map fork for Expo used with the Metro bundler
[Experimental] - 🚇 File crawling, watching and mapping for Metro
Relationship graph
Dependencies (left) and dependents (right) of walker.
Frequently installed together
Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.
Bindings for the Watchman file watching service
Lightweight debugging utility for Node.js and the browser
invariant
TypeScript definitions for node
TypeScript definitions for debug
A drop-in replacement for fs, making various improvements.
Convert Windows backslash paths to slash paths
Generated and versioned meta-package wrapping Metro
This packages is a collection of utilities and helper functions
This package contains shared types of Jest's packages.
Matches strings against configurable strings, globs, regular expressions, and/or functions
Release history
No releases in the last two years, typically about 98 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.8latest | 4 years ago | 5.7 KB | Apache-2.0 |
| 1.0.7 | 11 years ago | — | Apache-2.0 |
| 1.0.6 | 12 years ago | — | Apache-2.0 |
| 1.0.5 | 13 years ago | — | Apache-2.0 |
| 1.0.3 | 15 years ago | — | Apache-2.0 |
| 1.0.2 | 15 years ago | — | Apache-2.0 |
| 1.0.1 | 15 years ago | — | Apache-2.0 |
| 1.0.0 | 15 years ago | — | Apache-2.0 |
| 0.0.4 | 15 years ago | — | Apache-2.0 |
| 0.0.1 | 15 years ago | — | Apache-2.0 |
| 0.0.3 | 15 years ago | — | Apache-2.0 |
Overview
walker is an npm package that a simple directory tree walker. It has 3 known dependents in the graph. The latest version is 1.0.8, released under the Apache-2.0 license.
Who should use it
Teams working in the npm ecosystem who need a simple directory tree walker 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 (Apache-2.0).
- Lean dependency tree (2 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use walker?
No — walker should not be adopted for new projects. Last published 1782 days ago.
How do I install walker?
Run `npm install walker` to add walker to your npm project.
How many dependencies does walker have?
walker declares 2 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 14 KB on disk.
What license is walker released under?
walker is distributed under the Apache-2.0 license.
How popular is walker?
npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on walker.
Is walker still maintained?
The most recent release of walker (v1.0.8) was published 4 years ago.
Does walker run install scripts?
No. walker does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.