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

markdoc-traverse

v1.1.1

Published

A simple and tiny traversal library for MarkDoc AST

Downloads

16

Readme

A simple, tiny traversal library for Markdoc's AST

Installation

npm install markdoc-traverse

or

yarn add markdoc-traverse

or

pnpm add markdoc-traverse

Usage

Enter / Exit

Visit all nodes by passing an enter function.

Exit from the document node by passing a exit function. Useful for performing operations at the end of traversal

import { traverse } from "markdoc-traverse";
const ast = MarkDoc.parse(`
 Document
 ## Heading
 This is a level 2 heading
`);

traverse(ast, {
  enter(node) {
    // Visits all the nodes in the AST
  },
  exit(node) {
    // Exit after all nodes have been visited in document
  },
});

Nodes

Visit markdoc's nodes by passing any node as visitor

import { traverse } from "markdoc-traverse";

const ast = MarkDoc.parse(`
 Document
 ## Heading
 This is a level 2 heading
`);

traverse(ast, {
  heading: (node) => {
    // Your traversal logic
  },
  document: (node) => {
    // Your traversal logic
  },
});

Visitors are type safe , any makdoc nodes can be passed as a visitor with also option to enter and exit a node

import { traverse } from "markdoc-traverse";

const ast = MarkDoc.parse(`
 Document
 ## Heading
 This is a level 2 heading
`);

traverse(ast, {
  heading: {
    enter(node) {
      // Enter all heading nodes
    },
    exit(node) {
      // Exit at the end of each heading node
    },
  },
});

Tags

Visit MarkDocs tags configured inside your config file

traverse takes a third arugments which is a record of custom tags you would like to visit


import { traverse } from 'markdoc-traverse';

const ast = MarkDoc.parse(`
 {% callout %}
   `content`
 {% /callout %}
`)

const config = {
  tags: {
    callout
  }
};

traverse(ast,{
    callout:(node)=>{
       // Visit tags
    }
},{
  ...config.tags
})

tags are spread from your markdoc config

tags are type safe