Cherow NPM | npm.io

Cherow

A very fast and lightweight, standards-compliant, self-hosted javascript parser with high focus on both performance and stability.

Demo and Benchmark

Features

Conforms to the standard ECMAScript® 2019 (ECMA-262 9th Edition) language specification (draft)
Support for all stage 3 proposals via option.
JSX support via option.
Experimental feature support via option.
Optionally track syntactic node locations
Emits an ESTree-compatible abstract syntax tree.
Very well tested (~26 000 unit tests with full code coverage))
Supports all module loaders
Lightweight - ~70 KB minified (18 kb smaller than Acorn)

ESNext features

Stage 3 features support. These need to be enabled with the next option.

API

Cherow generates AST according to ESTree AST format, and can be used to perform syntactic analysis (parsing) of a JavaScript program, and with ES2015 and later a JavaScript program can be either a script or a module.

The parse method exposed by Cherow takes an optional options object which allows you to specify whether to parse in script mode (the default) or in module mode.

Here is a quick example to parse a script:

cherow.parseScript('g_plane = chinese');

// or

cherow.parse('x = async() => { for await (x of xs); }');

This will return when serialized in json:

{
    body: [{
        expression: {
            left: {
                name: 'x',
                type: 'Identifier'
            },
            operator: '=',
            right: {
                async: true,
                body: {
                    body: [{
                        await: true,
                        body: {
                            type: 'EmptyStatement',
                        },
                        left: {
                            name: 'x',
                            type: 'Identifier',
                        },
                        right: {
                            name: 'xs',
                            type: 'Identifier',
                        },
                        type: 'ForOfStatement',
                    }],
                    type: 'BlockStatement'
                },
                expression: false,
                generator: false,
                id: null,
                params: [],
                type: 'ArrowFunctionExpression'
            },
            type: 'AssignmentExpression'
        },
        type: 'ExpressionStatement'
    }],
    sourceType: 'script',
    type: 'Program'
}

Options

The second argument allows you to specify various options:

Option	Description
`module`	Enable module syntax
`loc`	Attach line/column location information to each node
`ranges`	Append start and end offsets to each node
`globalReturn`	Allow return in the global scope
`disableWebCompat`	Allows parsing without AnnexB
`impliedStrict`	Enable strict mode initial enforcement
`next`	Enable stage 3 support (ESNext)
`jsx`	Enable React JSX parsing
`source`	Set to true to record the source file in every node's `loc` object when the `loc option` is set.
`experimental`	Enable experimental features
`raw`	Attach raw property to each literal node and identifier node
`native`	Enable "native" NodeJS / V8 features
`directives`	Enable directive prologue to each literal node
`onComment`	Accept either callback or array to collect comment
`onToken`	Accept either callback or array and returns each found token

Contributing

If you feel something could've been done better, please do feel free to file a pull request with the changes.

Read our guidelines here

Bug reporting

If you caught a bug, don't hesitate to report it in the issue tracker. From the moment I respond to you, it will take maximum 60 minutes before the bug is fixed.

Note that I will try to respond to you within one hour. Sometimes it can take a bit longer. I'm not allways online. And if I find out it will take more then 60 minutes to solve your issue, you will be notified.

I know how irritating it can be if you are writing code and encounter bugs in your dependencies. And even more frustrating if you need to wait weeks or days.

Rationale

Existing parsers have many issues with them:

Acorn is the most commonly used tool out there because of its support for recent ES standards, but it's slow and it often is too permissive in what it accepts. It's also not optimized for handheld devices.
Esprima is a little faster than Acorn, but it's almost never updated, and their test suite has too many invalid tests. It also doesn't support recent ES standards.
Babylon is highly coupled to Babel, and is comparatively very slow and buggy, and failing to correctly handle even stable ECMAScript standard features.

None of these parsers would fare any chance against the official Test262 suite, and most fail a substantial number of them.

We figured we could try do better. We are used in plural form because Cherow is developed by a main developer and two others "behind the scenes" that contributes with their knowledge whenever it's necessary.