Project: micromark/micromark-extension-mdx-expression

Package: micromark-extension-mdx-expression@0.3.2

  1. Dependencies: 2·Dependents: 4
  2. micromark extension to support MDX or MDX JS expressions
  1. unified 169
  2. markdown 142
  3. mdx 29
  4. javascript 17
  5. micromark 16
  6. micromark-extension 16
  7. mdxjs 8
  8. ecmascript 7
  9. expression 5
  10. js 5
  11. es 3


Build Coverage Downloads Size Sponsors Backers Chat

micromark extension to support MDX (or MDX.js) expressions.

This package provides the low-level modules for integrating with the micromark tokenizer but has no handling of compiling to HTML: go to a syntax tree instead.

You should use this with mdast-util-mdx-expression (mdast). Alternatively, use either micromark-extension-mdx or micromark-extension-mdxjs with mdast-util-mdx to support all of MDX (or MDX.js). Or, use it through remark-mdx (remark).



npm install micromark-extension-mdx-expression


See mdast-util-mdx-expression for an example.



Support MDX (or MDX.js) expressions.

The export of syntax is a function that can be called with options and returns an extension for the micromark parser (to tokenize expressions; can be passed in extensions).


Acorn parser to use (Acorn, optional).


Options to pass to acorn (Object, default: {ecmaVersion: 2020, sourceType: 'module'}). All fields can be set. Positional info (loc, range) is set on ES nodes regardless of acorn options.


Whether to add an estree field to mdxFlowExpression and mdxTextExpression tokens with the results from acorn (boolean, default: false). Note that expressions can be empty or be just comments, in which case estree will be undefined.


This extensions support both MDX and MDX.js. The first is agnostic to the programming language (it could contain Rust or so), the last is specific to JavaScript. To turn on gnostic mode, pass acorn.

There are two types of expressions: in text (inline, span) or in flow (block). They start with {.

Depending on whether acorn is passed, expressions are either parsed in several tries until whole JavaScript is found (as in, nested curly braces depend on JS expression nesting), or they are counted and must be balanced.

Expressions end with }.

For flow (block) expressions, optionally markdown spaces ( or \t) can occur after the closing brace, and finally a markdown line ending (\r, \n) or the end of the file must follow.

While markdown typically knows no errors, for MDX it is decided to instead throw on invalid syntax.

Here is an expression in a heading:

## Hello, {1 + 1}!

In agnostic mode, balanced braces can occur: {a + {b} + c}.

In gnostic mode, the value of the expression must be JavaScript, so
this would fail: {!}.
But, in gnostic mode, braces can be in comments, strings, or in other
places: {1 /* { */ + 2}.

The previous examples were text (inline, span) expressions, they can
also be flow (block):

  1 + 1

This is incorrect, because there are further characters:

  1 + 1

Blank lines cannot occur in text, because markdown has already split them in
separate constructs, so this is incorrect: {1 +


In flow, you can have blank lines:

  1 +



Unexpected end of file in expression, expected a corresponding closing brace for {

This error occurs if a { was seen without a } (source: micromark-extension-mdx-expression, rule id: unexpected-eof). For example:

a { b

Could not parse expression with acorn: Unexpected content after expression

This error occurs when there is more content after a JS expression (source: micromark-extension-mdx-expression, rule id: acorn). For example:

a {"b" "c"} d

Could not parse expression with acorn: $error

This error occurs if acorn crashes (source: micromark-extension-mdx-expression, rule id: acorn). For example:

a {var b = "c"} d


Two tokens are used, mdxFlowExpression and mdxTextExpression, to reflect flow and text expressions.

They include:


See contributing.md in micromark/.github for ways to get started. See support.md for ways to get help.

This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.


MIT © Titus Wormer