fs-watch-tree 0.2.0

Recursively watch directories for changes

fs-watch-tree@0.2.0 was published on 2012-04-28. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is *.

Deprecated: This package is outdated and not actively maintained.

All fs-watch-tree versions · Permanent reference to 0.2.0 · Latest release

Package specifications

Version0.2.0
License declarationNot declared
Published2012-04-28T23:05:13.828Z
Node.js requirement*
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entry./lib/fs-watch-tree
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars22
Repository forks7

Install fs-watch-tree 0.2.0

npm install fs-watch-tree@0.2.0
pnpm add fs-watch-tree@0.2.0
yarn add fs-watch-tree@0.2.0

Runtime dependencies

  • when https://github.com/cujojs/when/tarball/1.0.2

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    OpenSSF repository checks

    Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

    Maintained0/10 — project is archived
    Code-Review0/10 — Found 2/30 approved changesets -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    Fuzzing0/10 — project is not fuzzed
    License9/10 — license file detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness