j-brooke

> Before I start - are you aware of a python port of your work? I'm not aware of any, but if you get one going, please let me know!

> OK I have a first pass which is essentially a manual port of your JS version to equivalent Python. Do you have tests you use? I don't have any...

Nice work. I'm good with the attribution how you've got it, thanks. The important thing is that people be able to move between the repos to find what they're looking...

Interesting. This is happening because the JavaScript version reads the document as JS data, before trying to produce output. In other word, it relies on `JSON.parse`. All numbers in JavaScript...

> This is because your number is greater than `Number.MAX_SAFE_INTEGER`. > > You could present your numbers only as strings and use a library like [bignumber.js](https://github.com/MikeMcl/bignumber.js/) to work with them,...

@shuckster Good thought. I hadn't known that the "reviver" parameter existed. Pity it doesn't look like it helps in this case.

Based on my testing, the NuGet package is already compatible with .NET 6. NuGet imports it fine. It compiles without any warnings. It runs on systems where only newer versions...

Hmm. I appreciate the info, but I don't know what to do with it. It's working for me with existing projects and brand new ones.

I've just pushed the v3.0.0 package to NuGet. It's set to netstandard2.0. Hopefully it gives you less trouble. If you choose to upgrade to it, please let me know how...

I'm closing this since I haven't heard anything new and the change to v3 hopefully fixed whatever it was.