[no-loss-of-precision] The rule reports false positives for values with numeric separators

Tell us about your environment

• ESLint Version: v7.1.0
• Node Version: v14.0.0
• npm Version: v6.14.4

What parser (default, Babel-ESLint, etc.) are you using?

@typescript-eslint/parser

Please show your full configuration:

It’s in a public repository: https://github.com/ridedott/eslint-config

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

const x = 1_000;

eslint --cache --cache-location './.cache/eslint' --fix '**/*.ts'

What did you expect to happen?

I expected not to see a no-loss-of-precision issue reported for this number.

What actually happened? Please include the actual, raw output from ESLint.

An issue is reported for this rule.

Are you willing to submit a pull request to fix this bug?

Yes, if the rule creator won’t do it themself 🙂

[kaicataldo]

As @anikethsaha mentions above, this is still currently experimental syntax. We will add support for this syntax in core rules once it reaches stage 4.

[anikethsaha]

I think it should be reported in typescript-eslint repo ?

cause numeric-separator is still in Stage 3 and eslint doesnt support stage 3 proposal .

also, the compiled JS for this TS code is working fine with eslint