Todo: Coverage does not work atm.
Esprima (esprima.org, BSD license) is a high performance, standard-compliant ECMAScript parser written in ECMAScript (also popularly known as JavaScript). Esprima is created and maintained by Ariya Hidayat, with the help of many contributors.
A fork of esprima (https://github.com/jquery/esprima), cause esprima has no new releases and many not merged pull req. if development/maintenance at jquery will start again, we maybe remove this fork.
- Rename to esprima-next
- generate a ESM build
- update npm packages
- disable npm run static-analysis && npm run dynamic-analysis, seem not to work after package update
- we don't need to support node <= 12
- ES2022 Class Properties & Privates
- Support numeric seperator and BigInt
- import assertions
following Pull reqs are merged from @esprima github:
- Export Esrpima Nodes type #2045
- Fix super() in non derived class #2047
- Support for ES2020 import.meta #2052
- Support for ES2020 export ns from #2055
- Fix parsing error in exponent expressions with unary left-hand sides. #2070
- bugfix import() #2076
- Support ES2021 Logical Assignment #2082
- ESM release support #2081
- Full support for ECMAScript 2019 (ECMA-262 10th Edition)
- Sensible syntax tree format as standardized by ESTree project
- Experimental support for JSX, a syntax extension for React
- Optional tracking of syntax node location (index-based and line-column)
- Heavily tested (~1600 unit tests with full code coverage)
Esprima can be used to perform lexical analysis (tokenization) or syntactic analysis (parsing) of a JavaScript program.
A simple example on Node.js REPL:
> var esprima = require('esprima-next');
> var program = 'const answer = 42';
> esprima.tokenize(program);
[ { type: 'Keyword', value: 'const' },
{ type: 'Identifier', value: 'answer' },
{ type: 'Punctuator', value: '=' },
{ type: 'Numeric', value: '42' } ]
> esprima.parseScript(program);
{ type: 'Program',
body:
[ { type: 'VariableDeclaration',
declarations: [Object],
kind: 'const' } ],
sourceType: 'script' }
For more information, please read the complete documentation.