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 🙏

© 2025 – Pkg Stats / Ryan Hefner

unist-find-node

v1.1.2

Published

Find node in MDAST by Position

Readme

unist-find-node

Find the nearest MDAST node matching the position (inline nodes excluded).

Install

npm:

npm i --save unist-find-node

Usage

See the following example as Example.md:

# hello, This is Markdown 
... any other texts
let vfile = require("to-vfile");
let unified = require("unified");
let parse = require("remark-parse");
let findNode = require("./index.js");


let assert = require("assert");

let tree = unified()
  .use(parse)
  .parse("Example.md");
let child = findNode(tree, { line: 1, column: 1 });

Then the child is the first heading node which would be intercepted as

let inspect = require("unist-util-inspect");
console.log(inspect(child));
// heading[1] (1:1-1:27, 0-26) [depth=1]
//   -- text: "hello, This is Markdown" (1:3-1:26, 2-25)

API

  child = findNode(node, position, customizeRules = [] )
  • node: the AST node parsed by unist
  • position: {line, column} an object with line and column property
  • customizeRules: An array of Functions customizing your rules for looking for nodes;
    It is an function of (node, parent) => true|fasle|null|undefined], taking node and its parent and return one of the four. Rules are executed sequetially in the array, and
    1. If a function returns true, then findNode return node;
    2. If a function returns flase, then findNode return parent
    3. If a function returns null, then findNode will stop executing following rules and try to find result in the node.children; If no result exists in node.children (when and only when position ranges of node.children does not cover positopn), then return node.
    4. If a function returns undefined, then findNode will continue following rules; If all rules return undefined, the node will continue to search at node.children; If no result exists in node.children, return node