When operating on it, the LosslessNumber will be converted into either a Number or BigInt, or an error will be thrown when it is unsafe to do so. This preserves any value, and even preserves the formatting like the trailing zero in the value 4.0. It takes a more flexible and powerful approach than the JSON BigInt solutions.īy default, lossless-json parses numbers into a lightweight LosslessNumber class, which holds the numeric value as a string.
The lossless-json library was developed specially for JSON Editor Online. Most of these libraries take a pragmatic approach, and parse long numbers straight into JavaScript’s relatively new BigInt data type. There are various excellent solutions for this available: lossless-json, json-bigint, js-json-bigint, or json-source-map. To solve this issue, you simply can’t use the built-in JSON.parse and you’ll have to use a different JSON parser instead. So by then, it is already too late and the value will be corrupted already. The problem though is that first the text is parsed into a number, and next, it is passed to the reviver. Like most web based JSON editors, it did also use the native JSON.parse function and regular JavaScript Numbers under the hood, so it suffered from the limitations explained above.Ī first thought may be: wait, but JSON.parse has an optional reviver argument, allowing you to parse content in a different way. This issue of parsing large numbers in JavaScript has been a recurring request from users of over the years. How can I prevent numbers from being corrupted by JSON.parse?
0 kommentar(er)
