Bug: Parser: End range of Program differs from Espree

[overlookmotel]

Before You File a Bug Report Please Confirm You Have Done The Following...

• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.
• I have searched for related issues and found none that matched my issue.
• I have read the FAQ and my problem is not listed.

Relevant Package

parser

Playground Link

https://typescript-eslint.io/play/#ts=5.7.2&showAST=es&fileType=.tsx&code=PTAEDMHtIKBgPOJQCMCGAnGQ&eslintrc=N4KABGBEBOCuA2BTAzpAXGYBfEWg&tsconfig=N4KABGBEDGD2C2AHAlgGwKYCcDyiAuysAdgM6QBcYoEEkJemy0eAcgK6qoDCAFutAGsylBm3TgwAXxCSgA&tokens=false

Repro Code

// foo

x

// bar

ESLint Config

tsconfig

Expected Result

The end location of Program differs between @typescript-eslint/parser and Espree.

Both TS-ESLint and Espree set the start location of Program as the first token, excluding whitespace and comments.

Espree sets the end location as the last token, also excluding whitespace and comments. However, @typescript-eslint/parser does not match that behavior - end location of Program is the end of the file.

I assume that @typescript-eslint/parser is aiming to align with Espree, and therefore this difference is unintentional.

Acorn does not exclude whitespace/comments from either start or end location. It's unfortunate the the 2 most-used ESTree-compatible parsers do not match each others' behavior, and personally I prefer the Acorn way - I think it's surprising that you can have comments which have locations outside the Program which contains them. But I imagine quite possible that neither Acorn nor Espree may want to make a breaking change.

Examples:

• @typescript-eslint/parser
• Espree
• Acorn

Actual Result

See above.

Additional Info

No response

Versions

package	version
@typescript-eslint/parser	8.29.0

[bradzacher]

It sounds to me like espree is wrong here?
Why would the range not include the comments and whitespace?

[overlookmotel]

Why would the range not include the comments and whitespace?

That is my feeling too. I'll raise an issue on Espree and see what they say.

However, at present @typescript-eslint/parser's behavior is half-and-half. It excludes whitespace/comments from the start range, but includes them in the end range. Whichever (include or exclude) is the "right" way to do it, the current behavior seems inconsistent.

[JLHwung]

Here is another case: with ranges option enabled:

// single comment

In espree: program.ranges are [0, 17] while ts-eslint gives [17, 17]