Bug: parsing a function with argument throws an error when `range` parse option is not set about typescript-eslint

[kirkwaiblinger]

Also reported on SO: https://stackoverflow.com/questions/78342447/im-using-typescript-eslint-parser-to-parse-a-typescript-function-how-can-i-ge#78434221

[bradzacher]

Duplicate of #8415
Please use the search

[ericmorand]

I did and I found the mentioned issue. But it was closed, and the issue is still happening.

[bradzacher]

Yes, but did you read the response in the issue which explains how to use it correctly and why it works this way...?

#8415 (comment)

[ericmorand]

I did not, you are right. I should have.

Out of curiosity, why not just fixing the issue - i.e. removing the range option and update the code so that the range is always emitted - since this is the only way to use the package anyway? Why leaving the option to the end user?

[bradzacher]

As mentioned in the linked comment

parser is not intended to be consumed by users - it's intended for use as an eslint parser.
...
if you just want the AST - use our typescript-estree package instead (parser is just a wrapper on top of that package). This package is intended for user consumption as a parser.