Package Exports
- cherow
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (cherow) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Cherow is a very fast, standard-compliant ECMAScript parser written in ECMAScript.
It strictly follows the ECMAScript® 2018 Language Specification and should parse according these specifications
It's safe to use in production.
Note! if you find a bug, open a issue ticket and we will try our best to solve it within 30 - 60 minutes.
A online demo can be found here.
Features
- Full support for ECMAScript® 2018 (ECMA-262 8th Edition)
- Stage 3 proposals (experimental)
- Support for JSX, a syntax extension for React
- Skips shebang comment nodes by default
- Optional tracking of syntax node location (index-based and line-column)
- 5100 unit tests with full code coverage
ESNext features
Stage 3 features support. This need to be enabled with the next option
- Import()
- Asynchronous Iteration
- Rest/Spread Properties
- Optional catch binding
- Regular Expression's new
DotAllflag
V8 experimental features
This need to be enabled with the v8 option
- Do expressions
Options
next- EnablesECMAScript Nextsupport and let you use proposals atstage 3or higher such asDynamic Importraw- Enables the raw property on literal nodes (Esprima and Acorn feature)comments- Enables option to collect comments. Optional; Either array or function. Works like Acorn onCommenttokens- If enabled each found token will be returned as either an function or an array (work in progres)ranges- Enables the start and characters offsets on the AST nodelocations- Enables location trackingjsx- Enables JSX
API
Cherow can be used to perform syntactic analysis of JavaScript program.
Note! there does not exist an sourceType: module option for parsing module code. According the ECMAScript specs you should use either parseScript or parseModule.
// Parsing script
cherow.parseScript('const fooBar = 123;');
// Parsing module code
cherow.parseModule('const fooBar = 123;');
Parsing with options
// Parsing script
cherow.parseScript('const fooBar = 123;', { ranges: true, raw: true, next: true});
Comments
Single line, multiline and HTML comments are supported, and can be collected as well. Shebang comment node - #!foo - are
skipped by default, and can't be collected.
Collecting comments
Collecting comments works just the same way as for Acorn.
// Function
cherow.parseScript('// foo',
{
comments: function(type, comment, start, end) {}
}
);
// Array
const commentArray = [];
cherow.parseScript('// foo',
{
comments: commentArray
}
);
Acorn and Esprima differences
The main difference between Cherow and Acorn and Esprima is that the mention libraries either doesn't parse everything according to TC39, or they doesn't fail as they should according to the ECMAScript specs.
Cherow parses everything after the specs, and fails 90% after the specs (work in progress).
Performance and benchmarks
The most important thing for an ECMAScript parser is the performance. Especially important is it when the parser is a dependency in other libraries. Poor performance will slow down the main library.
Cherow has been developed from scratch with only one goal - performance.
You can find the benchmarks here.
ESTree
Cherow outputs a sensible syntax tree format as standardized by ESTree project, and does not add any "extra" properties to any of its nodes.
However there is a small difference from other parsers because Cherow outputs a await property on the ForStatement node.
This because of the Asynchronous Iteration implementation.
Contribution
You are welcome to contribute. As a golden rule - always run benchmarks to verify that you haven't created any bottlenecks or did something that you shouldn't.
Terms of contribution:
- Think twice before you try to implement anything
- Minimum 1.5 mill ops/sec for light weight cases, and 800k - 1 mill ops/sec for "heavy" cases
- Avoid duplicating the source code
- Create tests that cover what you have implemented