eslint-plugin-big-number-rules VS break_eternity.js

And they did bite me, so I wrote this eslint plugin to help out a FinTech app that was experiencing a number of such bugs.

Either avoid floating-point, perhaps using BigInt, or use a library like BigNumber.js. (Incidentally, I wrote an eslint plugin to enforce its use.)

I wrote an eslint plugin for it.

For example, say you want to avoid using native arithmetic in your finance calculations to avoid the infamous binary-floating-point problems. There's no way to get standard.js to warn you about that. But (warning: self promotion) an eslint plugin can be written to do that for you. :)

For more details, see https://github.com/Patashu/break_eternity.js

That said, if you're looking for even bigger numbers, you could try potting break_eternity.js to c#, which would give you numbers so high you can't even describe them in terms of the exponent. Each number takes 3 floats worth of space, but can have numbers so high you would need e308 "e"s to show the limit.

You can have a look at tetration implementation in break_eternity.js by Patashu.

Looks like that's well within the range of break_eternity.js, but probably neither break_infinity.js nor logarithmica_numerus used by Aarex, and beyond break_break_infinity.js as well.