This is a pretty normal parse when we encounter syntax where an identifier is mandatory. You'd see the same for e.g.

export { x as }

the second Identifier has an empty span

@RyanCavanaugh I don't believe that's an equivalent example because this is an array. Nowhere else in the AST does this to my knowledge.

This would be like:

export { };

Parsing as:

NamedExports {
    elements: [
        ExportSpecifier {
            pos: 8,
            end: 8,
        }
    ]
}

Instead of:

// (this is what it does and is correct)
NamedExports {
    elements: []
}

This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow.

A better example is

class C<> {

}

Which does produce an empty array for typeParameters.

I want to fix it, Can I take this?

Give it a shot!

@Rustin-Liu are you still working on this? If not, I'd like to take a shot a this.

@Rustin-Liu are you still working on this? If not, I'd like to take a shot a this.

Please feel free take it.

@Ivan-Z are you still working on this? If not, I'm gonna give it a shot.