npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

walk-dir

v0.0.10

Published

"Walk" through a directory, revealing the contained folders and files in a practical way

Downloads

19

Readme

walk-Dir

NPM-Module used to "walk" through a directory, revealing the contained folders and files in a practical way.

Why

Oftentimes when working with a node.js application, it is necessary to retrieve the structure of a certain folder in an easy-to-parse form. This is useful e.g. when building an express.js-router or for bootstrapping child-modules automatically.

##Setup Install walkDir via npm install walk-dir --save

Make sure not to confuse this module with "walkdir", this is "walk-dir"!

Usage

  1. Require walkDir using var walkDir = require("walkdir");

  2. Choose one of the following methods it provides:

    2.1 List

     `walkDir.list(excludedPath, includedPath, depth)`
        
    • excludedPath: beginning of your search-path which should not be included in the results.

    • includedPath: end of your search-path which should be included in the results.

    • depth: At what level of depth should the recursive search end?

      • 0: Never. End when all subdirectories have been found and listed.
      • x: End after peeking into x levels of folders, 1 being the provided path
    • returns: Array of Strings representing the paths to found folders and files

    2.2 Tree

         `walkDir.tree(excludedPath, includedPath, depth)`
    • excludedPath: beginning of your search-path which should not be included in the results.
    • includedPath: end of your search-path which should be included in the results.
    • depth: At what level of depth should the recursive search end?
      • 0: Never. End when all subdirectories have been found and listed.
      • x: End after peeking into x levels of folders, 1 being the provided path
    • returns: JS-Object-tree where folders are branches and leaves are "true". -> Full paths are built from object-keys.
  3. Decide on using the synchronous, promise-based or callback-based version

    3.1 Synchronous

    • All methods are available as Synchronous versions by simply appending "Sync" to it
    • e.g. listSync, treeSync

    3.2 Promises

    • All methods return promises
    • simply use them to react to success/failure of the given method
    • e.g. list(...).then(function(result){/** do sth with result **/ }).catch(function(err){/** react to error **/)

    3.3 Callbacks

    • All methods accept a callback-function as optional last argument
    • simply pass this function using the signature function(err, result){...}
    • e.g. list(..., function(err, result){/** do sth with result if !err */})