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

@moyuyc/walk-tree

v1.0.3

Published

Enhanced and multifunctional tree walker

Downloads

47

Readme

@moyuyc/walk-tree

Build status Test coverage NPM version NPM Downloads Prettier Conventional Commits

Enhanced and multifunctional tree walker

Installation

npm install @moyuyc/walk-tree
# or use yarn
yarn add @moyuyc/walk-tree

Usage

const walkTree = require('@moyuyc/walk-tree')

walkTree(
  {
    name: 'root',
    children: [{ name: 'c1' }, { name: 'c2' }, { name: 'c3', children: { name: 'c31' } }]
  },
  node => {
    console.log(node.name)
  }
)
// prints
// root / c1 / c2 / c3 / c31
// by order

API

walk

index.js:54-138

Parameters

  • tree {T} - Type T should extends Object
  • walker {(node, ctx: Context) => {}} - Iterator for each node by order
  • opts Object {object}
    • opts.path {string} - The child's path on recursive struction (optional, default 'children')
    • opts.order {'pre' | 'post' | 'bfs'} pre means walking the node before walking it's children node by dfs post means walking the node after walking it's children node by dfs bfs means walking the node by bfs (optional, default 'pre')
    • opts.skipVisited {boolean} Should skip the node which has been visited. (optional, default true)
    • opts.uniquePath {Function | string | null} The unique's path for determining the node has been visited (same node) (optional, default node=>node)
    • opts.state {any} Inject in context.state on customized way

Returns any walkedTree {T}

Context

A traversal context.

Four operations are available. Note that depending on the traversal order, some operations have no effects.

remove

walk(rootNode, (node, ctx) => {
  if (node.name === 'remove-me') {
    return ctx.remove()
  }
})

replace

walk(rootNode, (node, ctx) => {
  if (node.name === 'replace-me') {
    return ctx.replace({ name: 'new-me' })
  }
})

break

Stop traversal now.

walk(rootNode, (node, ctx) => {
  if (node.name === 'stop') {
    return ctx.break()
  }
})

skip

Skip current node, children won't be visited.

walk(rootNode, (node, ctx) => {
  if (node.name === 'skip') {
    return ctx.skip()
  }
})

parent

Get the parent of the current node.

depth

Get the depth of the current node. The depth is the number of ancestors the current node has.

level

Get the level of current node. The level is the number of ancestors+1 the current node has.

index

Get the index of the current node.

Credit

The core algorithm of traverse credits to tree-crawl

walk-tree has the different with tree-crawl

Because tree-crawl has no idea about the intrinsic structure of your tree, you have to remove the node yourself. Context#remove only notifies the traversal code that the structure of the tree has changed.

Otherwise walk-tree would infers your tree by option path so don't requires additional remove action.

Authors

This library is written and maintained by imcuttle, mailto:[email protected].

License

MIT