src/content/docs/linter/rules/no-precision-loss.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.0.0` - Diagnostic Category: [`lint/correctness/noPrecisionLoss`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule doesn't have a fix. - The default severity of this rule is [**error**](/reference/diagnostics#error). - Sources: - Same as [`no-loss-of-precision`](https://eslint.org/docs/latest/rules/no-loss-of-precision) - Same as [`@typescript-eslint/no-loss-of-precision`](https://typescript-eslint.io/rules/no-loss-of-precision) - Same as [`lossy_float_literal`](https://rust-lang.github.io/rust-clippy/master/#lossy_float_literal){
"linter": {
"rules": {
"correctness": {
"noPrecisionLoss": "error"
}
}
}
}
Disallow literal numbers that lose precision
const x = 9007199254740993
const x = 5.123000000000000000000000000001
const x = 0x20000000000001
const x = 0x2_000000000_0001;
const x = 12345
const x = 123.456
const x = 123e34
const x = 12300000000000000000000000
const x = 0x1FFFFFFFFFFFFF
const x = 9007199254740991
const x = 9007_1992547409_91