Project: syntax-tree/estree-util-build-jsx

Package: estree-util-build-jsx@2.2.2

  1. Dependents: 0
  2. Transform JSX in estrees to function calls (for react, preact, and most hyperscript interfaces)
  1. tree 44
  2. ast 37
  3. javascript 26
  4. jsx 18
  5. compile 14
  6. react 14
  7. ecmascript 10
  8. xml 10
  9. estree 9
  10. hyperscript 5
  11. preact 5
  12. build 3
  13. acorn 3
  14. espree 2
  15. recast 2


Build Coverage Downloads Size Sponsors Backers Chat

estree utility to turn JSX into function calls: <x /> -> h('x')!


What is this?

This package is a utility that takes an estree (JavaScript) syntax tree as input that contains embedded JSX nodes (elements, fragments) and turns them into function calls.

When should I use this?

If you already have a tree and only need to compile JSX away, use this. If you have code, use something like SWC or esbuild instead.


This package is ESM only. In Node.js (version 16+), install with npm:

npm install estree-util-build-jsx

In Deno with esm.sh:

import {buildJsx} from 'https://esm.sh/estree-util-build-jsx@3'

In browsers with esm.sh:

<script type="module">
  import {buildJsx} from 'https://esm.sh/estree-util-build-jsx@3?bundle'


Say we have the following example.jsx:

import x from 'xastscript'

  <album id={123}>
    <name>Born in the U.S.A.</name>
    <artist>Bruce Springsteen</artist>
    <releasedate date="1984-04-06">April 6, 1984</releasedate>

    {1 + 1}
    <self-closing />
    <x name key="value" key={expression} {...spread} />

…and next to it a module example.js:

import fs from 'node:fs/promises'
import jsx from 'acorn-jsx'
import {fromJs} from 'esast-util-from-js'
import {buildJsx} from 'estree-util-build-jsx'
import {toJs} from 'estree-util-to-js'

const doc = String(await fs.readFile('example.jsx'))

const tree = fromJs(doc, {module: true, plugins: [jsx()]})

buildJsx(tree, {pragma: 'x', pragmaFrag: 'null'})


…now running node example.js yields:

import x from "xastscript";
console.log(x("album", {
  id: 123
}, x("name", null, "Born in the U.S.A."), x("artist", null, "Bruce Springsteen"), x("releasedate", {
  date: "1984-04-06"
}, "April 6, 1984")));
console.log(x(null, null, 1 + 1, x("self-closing"), x("x", Object.assign({
  name: true,
  key: "value",
  key: expression
}, spread))));


This package exports the identifier buildJsx. There is no default export.

buildJsx(tree[, options])

Turn JSX in tree into function calls: <x /> -> h('x')!


In almost all cases, this utility is the same as the Babel plugin, except that they work on slightly different syntax trees.

Some differences:


Nothing (undefined).


Configuration (TypeScript type).

👉 Note: you can also configure runtime, importSource, pragma, and pragmaFrag from within files through comments.


Choose the runtime (Runtime, default: 'classic').

Comment form: @jsxRuntime theRuntime.


Place to import jsx, jsxs, jsxDEV, and Fragment from, when the effective runtime is automatic (string, default: 'react').

Comment form: @jsxImportSource theSource.

👉 Note: /jsx-runtime or /jsx-dev-runtime is appended to this provided source. In CJS, that can resolve to a file (as in theSource/jsx-runtime.js), but for ESM an export map needs to be set up to point to files:

// …
"exports": {
  // …
  "./jsx-runtime": "./path/to/jsx-runtime.js",
  "./jsx-dev-runtime": "./path/to/jsx-runtime.js"
  // …

Identifier or member expression to call when the effective runtime is classic (string, default: 'React.createElement').

Comment form: @jsx identifier.


Identifier or member expression to use as a symbol for fragments when the effective runtime is classic (string, default: 'React.Fragment').

Comment form: @jsxFrag identifier.


When in the automatic runtime, whether to import theSource/jsx-dev-runtime.js, use jsxDEV, and pass location info when available (boolean, default: false).

This helps debugging but adds a lot of code that you don’t want in production.


File path to the original source file (string, example: 'path/to/file.js'). Passed in location info to jsxDEV when using the automatic runtime with development: true.


How to transform JSX (TypeScript type).

type Runtime = 'automatic' | 'classic'


Example: use with Acorn

To support configuration from comments in Acorn, those comments have to be in the program. This is done by espree but not automatically by acorn:

import {Parser} from 'acorn'
import jsx from 'acorn-jsx'

const doc = '' // To do: get `doc` somehow.

const comments = []
const tree = Parser.extend(jsx()).parse(doc, {onComment: comments})
tree.comments = comments


This package is fully typed with TypeScript. It exports the additional type Options and Runtime.


Projects maintained by the unified collective are compatible with maintained versions of Node.js.

When we cut a new major release, we drop support for unmaintained versions of Node. This means we try to keep the current release line, estree-util-build-jsx@^3, compatible with Node.js 166.


This package is safe.


See contributing.md in syntax-tree/.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