- 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 (~46 000 unit tests with full code coverage))
- Supports all module loaders
- Lightweight - ~70 KB minified (18 kb smaller than Acorn)
Stage 3 features support. These need to be enabled with the
- Numeric Separators
Experimental features support as in
NodeJS. These need to be enabled with the
Here is a quick example to parse a script:
This will return when serialized in json:
body:expression:left:name: 'x'type: 'Identifier'operator: '='right:async: truebody:body:await: truebody:type: 'EmptyStatement'left:name: 'x'type: 'Identifier'right:name: 'xs'type: 'Identifier'type: 'ForOfStatement'type: 'BlockStatement'expression: falsegenerator: falseid: nullparams:type: 'ArrowFunctionExpression'type: 'AssignmentExpression'type: 'ExpressionStatement'sourceType: 'script'type: 'Program'
The second argument allows you to specify various options:
||Enable module syntax|
||Attach line/column location information to each node|
||Append start and end offsets to each node|
||Allow return in the global scope|
||Allow to skip shebang - '#'|
||Enable strict mode initial enforcement|
||Enable stage 3 support (ESNext)|
||Enable React JSX parsing|
||Create a top-level error array containing all "skipped" errors|
||Set to true to record the source file in every node's
||Enable experimental features|
||Attach raw property to each literal node|
||Attach raw property to each identifier node|
||Allow to bypass scoping when run in a NodejS environment|
Cherow contains 3 different builds:
||The active development branch. You can and will expect bugs with this branch because it's not stable|
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
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.
Existing parsers have many issues with them:
Acornis 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.
Esprimais 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.
Babylonis 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 scene" that contributes with their knowledge whenever it's necessary.