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

treeverse

v3.0.0

Published

Walk any kind of tree structure depth- or breadth-first. Supports promises and advanced map-reduce operations with a very small API.

Downloads

10,501,058

Readme

treeverse

Walk any kind of tree structure depth- or breadth-first. Supports promises and advanced map-reduce operations with a very small API.

Treeverse does not care what kind of tree it is, it will traverse it for you just fine. It does the right thing with functions that return Promises, and returns a non-Promise value if your functions don't return Promises.

Rather than imposing a specific structure, like requiring you to have child nodes stored in a children array, it calls the supplied getChildren() function, so the children can be anywhere (or not even exist yet!) This makes it suitable for creating an optimized tree from a set of dependency manifests, for example.

USAGE

const {depth, breadth} = require('treeverse')

// depth-first traversal
// returns a promise if any visit/leave function returns a promise
// otherwise returns the result of leave, or visit if no leave function
// provided.
depth({
  // the root node where we start the traversal
  tree: rootNode,

  visit (node) {
    // optional
    // called upon descent into the node.
    // return a promise, or a mapped value, or nothing to just leave it
    // as-is
  },
  leave (node, children) {
    // optional
    // called as we ascend back to the root of the tree.
    // return a promise, or a reduced value, or nothing to leave it as is
    // the children array is a list of the child nodes that have been
    // visited (and potentially left) already.  If the tree is acyclic,
    // then leave() will have been called on all of them.  If it has
    // cycles, then the children may not have been left yet.
  },
  getChildren (node, nodeResult) {
    // required
    // return an array of child nodes in the tree, if any exist
    // returning a promise is totally ok, of course.
    // the first argument is the original value of the node.  The second
    // argument is the result of visit(node).
  },
  filter (node) {
    // optional
    // return true if the node should be visited, false otherwise
    // initial tree is always visited, so this only filters children
    // note that filtering a node _also_ filters all of its children.
  },
})

// breadth first traversal
// returns a promise if any visit function returns a promise
// otherwise returns the result of the top-level node.
// note that only a visit() function is supported here, since a node's
// children are typically traversed much later in the process.
breadth({
  // the root node where we start the traversal
  tree: rootNode,

  visit (node) {
    // optional, but a no-op if not provided.
    // called when this node is encountered in the traversal.
    // return a promise, or a mapped value, or nothing to leave as-is.
  },
  getChildren (node, nodeResult) {
    // required, same as depth()
  },
  filter (node) {
    // optional, same as depth()
  },
})

API

Both functions take a single options object as an argument, and return either the result value, or a Promise to the result value if the methods in the options argument ever return a Promise.

  • treeverse.breadth - Perform a breadth-first traversal. That is, walk across node siblings before traversing node children.
  • treeverse.depth - Perform a depth-first traversal. That is, walk down into child nodes before traversing siblings.

OPTIONS

All function options can return a Promise or actual value.

The return value is the result of the top level visit function if no leave function is provided, or leave. If any method along the way returns a promise, then the top level function will return a promise which resolves to the result of visiting (and leaving) the top node in the tree.

  • tree - The initial node where the traversal begins.
  • visit(node) - Function to call upon visiting a node.
  • leave(node, children) - (Depth only) Function to call upon leaving a node, once all of its children have been visited, and potentially left. children is an array of child node visit results. If the graph is cyclic, then some children may have been visited but not left.
  • getChildren(node, nodeResult) - Get an array of child nodes to process.
  • filter - Filter out child nodes from the traversal. Note that this filters the entire branch of the tree, not just that one node. That is, children of filtered nodes are not traversed either.

STACK DEPTH WARNING

When a leave method is specified, then recursion is used, because maintaining state otherwise is challenging. This means that using leave with a synchronous depth first traversal of very deeply nested trees will result in stack overflow errors.

To avoid this, either make one or more of the functions async, or do all of the work in the visit method.

Breadth-first traversal always uses a loop, and is stack-safe.

It is possible to implement depth first traversal with a leave method using a loop rather than recursion, but maintaining the leave(node, [children]) API surface would be challenging, and is not implemented at this time.