Repository navigation
Any plans to support larger than 53-bit integers? #278
Description
Integers larger than 53 bits are valid JSON, but when parsed by JSON.parse they get truncated down to 53 bits and lose a few least significant digits. We have 64 bit integers coming from our backend and use https://www.npmjs.com/package/json-bigint to parse, any chance of adding an option for replace the built-in JSON.parse with a custom function, or just a boolean option for using json-bigint?
Reacted by K.J. Valencik, Vent , Roy Breidi, Javier, Brandon Chinn, Sufiane, Abigail Willow, emergent_reasons, Doug Ludlow, Gogo and 1 more
Activity
kjvalencik commentedon Nov 16, 2017
Should just need to provide an option defaulted to
JSON.parse. Then you can bring your own JSONBigInt parser.kjvalencik commentedon Nov 20, 2017
Adding a
parseroption does make thereviveroption redundant since it could be accomplished with:jp-simons commentedon Nov 22, 2017
Right on, thanks!