banned VS bignumber.js

I don't care about being banned. Wouldn't be the first time https://github.com/guest271314/banned.

Or, more accurately, the "teams" I have joined have tended to get all bent out of shape when their narratives are questioned, and their errors and omissions are exposed on the record - so they have banned me and just closed my issues. E.g., https://github.com/guest271314/banned. Being banned from Node.js organization - after being invited to join the single executable "team" - was ridiculous.

On the other side of that coin, there are some developers who think their code is high and mighty to the degree that if/when you question their specification goal/non-goal narrative, point out ambiguity relevant to the third-party code they promote, or advise them the configuration process for their work is unnecessarily complicated, when JSON could be used they'll ban you. Ask me how I know https://github.com/guest271314/banned.

Like, he's his essay complaining that he can't post racial slurs on Github. https://github.com/guest271314/banned/issues/2

Yes, the Deno folks banned me. So did the Node.js folks, and many others https://github.com/guest271314/banned. Weak. I ain't mad. I vet spurious claims, without exception. I don't care who you think you are. Your claims are not above or below being tested and vetted, exposed.

If you are going to take the time to ban https://github.com/guest271314/banned/issues/7 the messenger that delivers the message you are advertising false claims you must have enough time to review third-party claims in advance.

Well, those are not viable reasons to be kicked off of a team, so they had to lie and say I "attacked" another user. Then lie some more and claim I "harassed" another user. https://github.com/guest271314/banned/issues/6

Most if not all of those bans should be documented here https://github.com/guest271314/banned.

If you use floating-points for currency (instead of whole-numbers like you probably should) libraries like bignumber.js help keep your code away from the binary floating-point pitfalls of IEEE-754 which manifests in the standard JavaScript number type:

This issue (well, another one in a widely used JS library) is what brought me to dig deeper into these "arbitrary precision" libraries and understand why this happens. I thought they were using rational numbers, but that's not the case. And this is what led me to think about how to solve this problem.

ERC20 has decimals fields and must be handled with digit awareness. I wanted to use only one library, but I used both ether.js's BigNumber and bignumber.js (for display purpose).

Most programming languages ( JavaScript, PHP, Go, Python, Java, C# ) have built-in support or 3rd-party libraries for handling this data type, even though the internal implementations can differ:

I'm working on a project where users will enter numbers like 9,999,999,999.99999 (up to 15 digits, up to 5 of them decimal) and we are having a problem with Numbers losing precision beyond certain number of digits (a typical issue for IEEE Standard 754 Floating Point Numbers, the 0.1 + 0.2 problem). I've solved this problem in a few projects before with the help of decimal.js or bignumber,js . In those cases, we kept user-input as strings and used a few custom-made numeric textbox widgets to accommodate this. Unfortunately, those widgets were proprietary... Now I need one again, but can't find anything. Do they exist?

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

To solve the problem while JavaScript waits on its own BigDecimal API, you can use something like bignumber.js to perform your calculations.

You need to use something like BigNumber.js