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

match-ast

v2.0.0

Published

Helper functions to verify an AST structure

Downloads

2,439

Readme

match-ast

Travis Prettier npm License

Collection of helper functions to verify a AST tree structure.

Usage

Type matchers

Example: verify if a tree represents a JSON.stringify() call

const {
  isCallExpression,
  isMemberExpression,
  isIdentifier
} = require("match-ast");

// Check if the tree represents a `JSON.stringify()` call.
const isJsonStringify = isCallExpression({
  callee: isMemberExpression({
    object: isIdentifier("JSON"),
    property: isIdentifier("stringify")
  })
});

Most functions are named isSomething where Something is the type of the node (i.e. isIdentifier checks if node.type === "Identifier"). They accept a single argument: an object where keys represent the property of a node and the value is a matcher for that property.

The accepted matchers are: a matcher function, primitive values, arrays or functions.

Calling a function with no arguments means it will only assert its type and none of the properties. For types with no properties (i.e. ThisExpression), arguments are ignored.

For nodes with only a single property (i.e. Identifier with property name), you can pass directly the matcher for that property, so you don't have to pass an object with a single property. For example, isIdentifier("foo") is equivalent to isIdentifier({ name: "foo" }).

Passing extra properties to a matcher will make it always return false:

// check() will always return false since there's no `name` property in CallExpression
const check = isCallExpression({ name: "foo" });

Other matchers

either

For cases where a node can be one of many values:

const { either, isIdentifier, isMemberExpression } = require("match-ast");

// Check if the three is a `JSON.stringify()` or `stringify()` call
const isStringify = isCallExpression({
  callee: either(
    isMemberExpression({
      object: isIdentifier("JSON"),
      property: isIdentifier("stringify")
    }),
    isIdentifier("stringify")
  )
});

Credits

This library consists of helper functions automatically generated on top of the excellent @babel/types definitions.