Acornima 1.6.2

👁 GitHub Actions Workflow Status
👁 NuGet Release
👁 Feedz Version
👁 Donate

👁 Stand With Ukraine

Acorn + Esprima = Acornima

This project is a crossbreeding of the acornjs and the Esprima.NET parsers, with the intention of creating an even more complete and performant ECMAScript (a.k.a JavaScript) parser library for .NET by combining the best bits of those.

It should also be mentioned that there is an earlier .NET port of acornjs, AcornSharp, which though is unmaintained for a long time, served as a good starting point. Had it not been for AcornSharp, this project would probably have never started.

Here is how this Frankenstein's monster looks like:

• The tokenizer is mostly a direct translation of the acornjs tokenizer to C# (with many bigger and smaller performance improvements, partly inspired by Esprima.NET) - apart from the regex validation/conversion logic, which has been borrowed from Esprima.NET.
• The parser is ~99% acornjs (also with a bunch of minor improvements) and ~1% Esprima.NET (strict mode detection, public API). It is also worth mentioning that the error reporting has been changed to use the error messages of V8.
• It includes protection against the non-catchable StackOverflowException using the same approach as Roslyn.
• Both parent projects follow the ESTree specification, so does Acornima. The actual AST implementation is based on that of Esprima.NET, with further minor improvements to the class hierarchy that bring it even closer to the spec and allow encoding a bit more information.
• The built-in AST visitors and additional utility features stems from Esprima.NET as well.

And what good comes out of this mix?

• A parser that matches the performance of Esprima.NET while doing more: it also passes the complete Test262 test suite for ECMAScript 2026.
• It is also more economic with regard to stack usage, so it can parse ~2x deeper structures.
• More options for fine-tuning parsing.
• A standalone tokenizer which can deal with most of the ambiguities of the JavaScript grammar (thanks to the clever context tracking solution implemented by acornjs).
• The parser tracks variable scopes to detect variable redeclarations. As of v1.1.0, it's able to expose the collected scope information to the consumer (see also this PR or this other example of usage).

Getting started

1. Install the package from NuGet

dotnet add package Acornima

Or, if you want to use additional features like JSX parsing, JavaScript generation from AST or AST to JSON conversion:

dotnet add package Acornima.Extras

2. Import the Acornima namespace in your application

using Acornima;

3. Create a parser instance

var parser = new Parser();

Or, if you want to tweak the available settings:

var parser = new Parser(new ParserOptions { /* ... */ });

4. Use the parser instance to parse your JavaScript code

var ast = parser.ParseScript("console.log('Hello world!')");

AST

Node [x]
 ├─AssignmentPattern : IDestructuringPatternElement [v,s]
 ├─CatchClause [v,s]
 ├─ClassBody [v,s]
 ├─ClassProperty : IClassElement, IProperty
 │ ├─AccessorProperty : IClassElement, IProperty [v,s]
 │ ├─MethodDefinition : IClassElement, IProperty [v,s]
 │ └─PropertyDefinition : IClassElement, IProperty [v,s]
 ├─Decorator [v,s]
 ├─DestructuringPattern : IDestructuringPatternElement
 │ ├─ArrayPattern : IDestructuringPatternElement [v,s]
 │ └─ObjectPattern : IDestructuringPatternElement [v,s]
 ├─ImportAttribute [v,s]
 ├─ModuleSpecifier
 │ ├─ExportSpecifier [v,s]
 │ └─ImportDeclarationSpecifier
 │ ├─ImportDefaultSpecifier [v,s]
 │ ├─ImportNamespaceSpecifier [v,s]
 │ └─ImportSpecifier [v,s]
 ├─Program : IHoistingScope [v]
 │ ├─Module : IHoistingScope [s,t=Program]
 │ └─Script : IHoistingScope [s,t=Program]
 ├─Property : IProperty
 │ ├─AssignmentProperty : IProperty [v,s,t=Property]
 │ └─ObjectProperty : IProperty [v,s,t=Property]
 ├─RestElement : IDestructuringPatternElement [v,s]
 ├─StatementOrExpression
 │ ├─Expression [x]
 │ │ ├─ArrayExpression [v,s]
 │ │ ├─ArrowFunctionExpression : IFunction [v,s]
 │ │ ├─AssignmentExpression [v,s]
 │ │ ├─AwaitExpression [v,s]
 │ │ ├─BinaryExpression [v]
 │ │ │ ├─LogicalExpression [s]
 │ │ │ └─NonLogicalBinaryExpression [s,t=BinaryExpression]
 │ │ ├─CallExpression : IChainElement [v,s]
 │ │ ├─ChainExpression [v,s]
 │ │ ├─ClassExpression : IClass [v,s]
 │ │ ├─ConditionalExpression [v,s]
 │ │ ├─FunctionExpression : IFunction [v,s]
 │ │ ├─Identifier : IDestructuringPatternElement [v,s]
 │ │ ├─ImportExpression [v,s]
 │ │ ├─Literal [v]
 │ │ │ ├─BigIntLiteral [s,t=Literal]
 │ │ │ ├─BooleanLiteral [s,t=Literal]
 │ │ │ ├─NullLiteral [s,t=Literal]
 │ │ │ ├─NumericLiteral [s,t=Literal]
 │ │ │ ├─RegExpLiteral [s,t=Literal]
 │ │ │ └─StringLiteral [s,t=Literal]
 │ │ ├─MemberExpression : IChainElement, IDestructuringPatternElement [v,s]
 │ │ ├─MetaProperty [v,s]
 │ │ ├─NewExpression [v,s]
 │ │ ├─ObjectExpression [v,s]
 │ │ ├─ParenthesizedExpression [v,s]
 │ │ ├─PrivateIdentifier [v,s]
 │ │ ├─SequenceExpression [v,s]
 │ │ ├─SpreadElement [v,s]
 │ │ ├─Super [v,s]
 │ │ ├─TaggedTemplateExpression [v,s]
 │ │ ├─TemplateLiteral [v,s]
 │ │ ├─ThisExpression [v,s]
 │ │ ├─UnaryExpression [v]
 │ │ │ ├─NonUpdateUnaryExpression [s,t=UnaryExpression]
 │ │ │ └─UpdateExpression [s]
 │ │ └─YieldExpression [v,s]
 │ └─Statement [x]
 │ ├─BlockStatement [v]
 │ │ ├─FunctionBody : IHoistingScope [v,s,t=BlockStatement]
 │ │ ├─NestedBlockStatement [s,t=BlockStatement]
 │ │ └─StaticBlock : IClassElement, IHoistingScope [v,s]
 │ ├─BreakStatement [v,s]
 │ ├─ContinueStatement [v,s]
 │ ├─DebuggerStatement [v,s]
 │ ├─Declaration [x]
 │ │ ├─ClassDeclaration : IClass [v,s]
 │ │ ├─FunctionDeclaration : IFunction [v,s]
 │ │ ├─ImportOrExportDeclaration
 │ │ │ ├─ExportDeclaration
 │ │ │ │ ├─ExportAllDeclaration [v,s]
 │ │ │ │ ├─ExportDefaultDeclaration [v,s]
 │ │ │ │ └─ExportNamedDeclaration [v,s]
 │ │ │ └─ImportDeclaration [v,s]
 │ │ └─VariableDeclaration [v,s]
 │ ├─DoWhileStatement [v,s]
 │ ├─EmptyStatement [v,s]
 │ ├─ExpressionStatement [v]
 │ │ ├─Directive [s,t=ExpressionStatement]
 │ │ └─NonSpecialExpressionStatement [s,t=ExpressionStatement]
 │ ├─ForInStatement [v,s]
 │ ├─ForOfStatement [v,s]
 │ ├─ForStatement [v,s]
 │ ├─IfStatement [v,s]
 │ ├─LabeledStatement [v,s]
 │ ├─ReturnStatement [v,s]
 │ ├─SwitchStatement [v,s]
 │ ├─ThrowStatement [v,s]
 │ ├─TryStatement [v,s]
 │ ├─WhileStatement [v,s]
 │ └─WithStatement [v,s]
 ├─SwitchCase [v,s]
 ├─TemplateElement [v,s]
 └─VariableDeclarator [v,s]

Legend:

• v - A visitation method is generated in the visitors for the node type.
• s - The node class is sealed. (It's beneficial to check for sealed types when possible.)
• t - The node type (the value of the Node.Type property) as specified by ESTree (shown only if it differs from the name of the node class).
• x - The node class can be subclassed. (The AST provides some limited extensibility for special use cases.)

JSX

The library also supports the syntax extension JSX. However, mostly for performance reasons, the related functionality is separated from the core parser: it is available in the Acornima.Extras package, in the Acornima.Jsx namespace.

Installation & usage

After installing the Acornima.Extras package as described in the Getting started section, you can parse JSX code like this:

using Acornima.Jsx;

var parser = new JsxParser(new JsxParserOptions { /* ... */ });

var ast = parser.ParseScript("<>Hello world!</>");

AST

Node [x]
 └─StatementOrExpression
 └─Expression [x]
 └─JsxNode [x]
 ├─JsxAttributeLike
 │ ├─JsxAttribute [v,s]
 │ └─JsxSpreadAttribute [v,s]
 ├─JsxClosingTag
 │ ├─JsxClosingElement [v,s]
 │ └─JsxClosingFragment [v,s]
 ├─JsxElementOrFragment
 │ ├─JsxElement [v,s]
 │ └─JsxFragment [v,s]
 ├─JsxEmptyExpression [v,s]
 ├─JsxExpressionContainer [v,s]
 ├─JsxName
 │ ├─JsxIdentifier [v,s]
 │ ├─JsxMemberExpression [v,s]
 │ └─JsxNamespacedName [v,s]
 ├─JsxOpeningTag
 │ ├─JsxOpeningElement [v,s]
 │ └─JsxOpeningFragment [v,s]
 └─JsxText [v,s]

Migration from Esprima.NET

Projects using Esprima.NET can be converted to Acornima relatively easily as the public API of the two libraries are very similar. (A pretty good proof of this statement is this PR, which migrates Jint to Acornima.)

The most notable changes to keep in mind with regard to migration are the following:

• The default value of the ParserOptions.RegExpParseMode property has been changed to RegExpParseMode.Validate.
• The default value of the ParserOptions.RegexTimeout property has been changed to 5 seconds.
• The default value of the ParserOptions.Tolerant property has been changed to false.
• The Location struct has been renamed to SourceLocation.
• The TokenType and CommentType enums have been renamed named to TokenKind and CommentKind, respectively. Also, some of the member names have been changed.
• The Token and Comment structs have been completely reworked. The SyntaxToken and SyntaxComment classes have been removed.
• The SyntaxElement class has been removed, that is, the Node class has become the root of the AST node type hierarchy. (This also means that tokens and comments are not attached to the root nodes of the AST. You can obtain those via the ParserOptions.OnToken and ParserOptions.OnComment callbacks).
• The Nodes enum has been renamed to NodeType.
• The Node.AssociatedData property has been renamed to UserData.
• The AssignmentOperator, BinaryOperator and UnaryOperator enums have been merged into a single enum named Operator. Also, some of the member names have been changed.
• The Literal node class has been changed to only provide an object? Value { get; } property for accessing literal value. There are sealed subclasses for the different kinds of literals. Use those to access literal values in a type-safe (and more efficient) manner.
• The Property node class has been made abstract and two sealed subclasses have been introduced: AssignmentProperty and ObjectProperty (for representing properties of object destructuring patterns and object literals, respectively). Also, the VisitProperty method has been replaced with VisitAssignmentProperty and VisitObjectProperty in visitors.
• Similar changes have been made to the BlockStatement node class. Two new sealed subclasses have been introduced: FunctionBody and NestedBlockStatement (for representing bodies of function expressions/declarations and actual block statements that occurs within function bodies, respectively). Also, to conform to the ESTree spec, StaticBlock has been changed to be a subclass of BlockStatement. The VisitBlockStatement method has been kept in visitors, but only NestedBlockStatement is dispatched to it. The other two subclasses has dedicated visitation methods (VisitFunctionBody and VisitStaticBlock).
• The ClassElement node base class has been replaced with the IClassElement interface.
• The Strict property of function expression/declaration node classes has been moved to FunctionBody.
• The JsxExpression node class has been renamed to JsxNode.
• The JsxElement node class has been renamed to JsxElementOrFragment and two sealed subclasses have been introduced: JsxElement and JsxFragment.
• The ParserException class has been renamed to ParseErrorException and been made abstract. Two concrete subclasses (SyntaxErrorException and RegExpConversionError) have been introduced to indicate different kinds of errors that can occur during parsing.
• The message format of the ParseErrorException class has been changed. The reported messages are translatable text resources, so it is not recommended to rely on them to determine the reason of the error. For such purposes, you can use the ParseErrorException.Error.Code property.
• The ParseErrorException.Column property has been changed to store zero-based indices. (The exception message still includes one-based column indices though.)

Benchmarks

BenchmarkDotNet v0.15.6, Windows 10
AMD Ryzen 7 7735HS with Radeon Graphics 3.20GHz, 1 CPU, 16 logical and 8 physical cores
.NET SDK 10.0.201
 [Host] : .NET 10.0.5 (10.0.5, 10.0.526.15411), X64 RyuJIT x86-64-v3
 .NET 10.0 : .NET 10.0.5 (10.0.5, 10.0.526.15411), X64 RyuJIT x86-64-v3

Job=.NET 10.0 Runtime=.NET 10.0 Toolchain=net10.0 
IterationCount=15 LaunchCount=2 WarmupCount=10 

Known issues and limitations

Regular expressions

The parser can be configured to convert JS regular expression literals to .NET Regex instances (see ParserOptions.RegExpParseMode). However, because of the fundamental differences between the JS and .NET regex engines, in many cases this conversion can't be done perfectly (or, in some cases, at all):

• Case-insensitive matching won't always yield the same results. Implementing a workaround for this issue would be extremely hard, if not impossible.
• The JS regex engine assigns numbers to capturing groups sequentially (regardless of the group being named or not named) but .NET uses a different, weird approach: "Captures that use parentheses are numbered automatically from left to right based on the order of the opening parentheses in the regular expression, starting from 1. However, named capture groups are always ordered last, after non-named capture groups." Without some adjustments, this would totally mess up numbered backreferences and replace pattern references. So, as a workaround, the converter wraps all named capturing groups in a non-named capturing group to force .NET to include all the original capturing groups in the resulting match in the expected order. (Of course, this won't prevent named groups from being listed after the numbered ones.) If needed, the original number of groups can be obtained from the returned RegExpParseResult object's ActualRegexGroupCount property.
• The characters allowed in group names differs in the two regex engines. For example, the group name $group is valid in JS but invalid in .NET. So, as a workaround, the converter encodes the problematic group names to names that are valid in .NET and probably won't collide with other group names present in the pattern. For example, $group is encoded like __utf8_2467726F7570. The original group names can be obtained using the returned RegExpParseResult object's GetRegexGroupName method.
• Self-referencing capturing groups like /((a+)(\1) ?)+/ may not produce the exact same captures. RegexOptions.ECMAScript is supposed to cover this, however even the MSDN example doesn't produce the same matches. (As a side note, RegexOptions.ECMAScript is kind of a false promise, it can't even get some basic cases right by itself.)
• Similarily, repeated nested groups like /((a+)?(b+)?(c))*/ may produce different captures for the groups. (JS has an overwrite behavior while .NET doesn't).
• .NET treats forward references like \1(\w) differently than JS and it's not possible to convert this kind of patterns reliably. (The converter could make some patterns work by rewriting them to something like (?:)(\w) but there are cases where even this wouldn't work.)
• Unicode mode issues:
  • There could be false positive empty string matches in the middle of surrogate pairs. Patterns as simple as /a?/u will cause this issue when the input string contains astral Unicode chars. There is no out-of-the-box workaround for this issue but it can be mitigated somewhat using a bit of "post-processing", i.e., by filtering out the false positive matches after evaluation like it's done here. Probably there is no way to improve this situation until .NET adds the option to treat the input string as Unicode code points.
  • Support for Unicode property escapes is pretty limited (see explanation). Currently, only General Category expressions are converted. But even this is not perfect as the result will depend the Unicode version included in the specific .NET runtime which is executing the parser's code.

To sum it up, legacy pattern conversion is pretty solid apart from the minor issues listed above. However, support for unicode mode (flag u) patterns is partial and quirky, while conversion of the upcoming unicode sets mode (flag v) will be next to impossible - until the .NET regex engine gets some improved Unicode support.

Any feedback appreciated, contributions are welcome!