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

remark-ast-inline

v0.0.1

Published

An experimental package for adding nodes and values to a mdast from template strings.

Downloads

9

Readme

remark-ast-inline

An experimental package for adding nodes and values to a abstract syntax tree from template expressions, via a unified parser of the kind exposed by remark.

Usage

Import

import rai from 'remark-ast-express'

Configure

const md = rai({
  converter // Optional
})

function converter(value) {
  return { type: 'value', value: value }
}

The converter function is called (if present) with all the expressions that would be inserted into your template string. It can return either an unist node (an object with a type field containing a string) to later be inserted into the AST or a value to be inserted into the string. For example, to make this package completely useless:

function converter(value) {
  return String(value) // Can't just be `return value` or nodes would still be inserted.
)

Process Text

let { string, astInserter } = md`\
# This is some markdown...
I'm going to insert a value into the AST riiight ${"foobar"}here.

${{
  type: 'strong',
  children: [{type: 'text', value: 'not here'}]
}}
`

import remark from 'remark'
 
let tree = remark()
  .use(...others...)
  .use(astInserter) // The plugin returned above should be last
  .parse(string) // The exact(!) string returned above

Gives:

{
  "type": "root",
  "children": [
    {
      "type": "heading",
      "depth": 1,
      "children": [
        {
          "type": "text",
          "value": "This is some markdown...",
          "position": ...
        }
      ],
      "position": ...
    },
    {
      "type": "paragraph",
      "children": [
        {
          "type": "text",
          "value": "I'm going to insert a value into the AST riiight ",
          "position": ...
        },
        {
          "type": "value",
          "value": "foobar",
          "position": ...
        },
        {
          "type": "text",
          "value": "here.",
          "position": ...
        }
      ],
      "position": ...
    },
    {
      "type": "paragraph",
      "children": [
        {
          "type": "value",
          "value": {
            "type": "strong",
            "children": [
              {
                "type": "text",
                "value": "not here"
              }
            ]
          },
          "position": ...
        }
      ],
      "position": ...
    }
  ],
  "position": ...
}

Or, with no converter:

{
  "type": "root",
  "children": [
    {
      "type": "heading",
      "depth": 1,
      "children": [
        {
          "type": "text",
          "value": "This is some markdown...",
          "position": ...
        }
      ],
      "position": ...
    },
    {
      "type": "paragraph",
      "children": [
        {
          "type": "text",
          "value": "I'm going to insert a value into the AST riiight foobarhere.",
          "position": ...
        }
      ],
      "position": ...
    },
    {
      "type": "paragraph",
      "children": [
        {
          "type": "strong",
          "children": [
            {
              "type": "text",
              "value": "not here"
            }
          ],
          "position": ...
        }
      ],
      "position": ...
    }
  ],
  "position": ...
}

WTF? Why?

Well, this gives you a nice(ish) syntax in vanilla Javascript for programmatically inserting nodes into the AST inline; which might be useful...? I'm considering using it to implement a React/JS+Markdown website templating framework; it was the least awkward way to hack something together that I may like more than the alternatives (e.g. MDX).

How?

The code inserts tokens of the form <[prefix]:[index]> into the string, where the prefix is a random alphabetic (upper and lower) string that occurs nowhere else in the string (same across the tokens) and the index corresponds to which node should be inserted there. A prefix string and nodes array fields are included in the tag function output.