Overview

https://typescript-eslint.io/rules/no-loss-of-precision states that it exists to add support fornumeric separators to the baseeslint/no-loss-of-precision rule. But, numeric separators have passed stage 3 and are natively supported in ESLint I believe. [Example ESLint playground with the rule working on a number with a numeric separator]

tl;dr: I propose we remove the ruleextension because the base rule contains all its features.

👉 I'm not proposing we remove the base rule (or ask ESLint to)

Whether it exists in popular configs such as eslint-config-airbnb-typescript and eslint-config-standard-with-typescript

• eslint-config-airbnb-typescript: yes,https://github.com/iamturns/eslint-config-airbnb-typescript/blob/8ef77c928c97d977f053c9c638831363a715d4a9/lib/shared.js#L143
• eslint-config-standard-with-typescript: yes,https://github.com/standard/eslint-config-standard-with-typescript/blob/b7b298d13ec737684e4368c726a3a9a66cd2f465/src/index.ts#L16

Sourcegraph queries showing how often it appears in user configs

Sourcegraph query showing it used in <200 repos: this doesn't seem like a particularly common rule for users to explicitly specify. That makes sense to me given that it's in the base recommended config (and has been for a while).