Avoid appending n to BigInt values in the JSON viewer

[Assem-Uber]

Description:

BigInt is JavaScript's way of handling large numbers, but it is not part of the JSON specification. When a JSON payload is received from a language that supports long numeric values, those values are often represented as numbers. In JavaScript, these numbers might be converted to BigInt for internal use.

However, when displaying these values to end users in a JSON viewer, appending n (indicating BigInt) can be confusing. Users may not be aware of the specifics of BigInt or JavaScript's implementation details. What matters to the users is that these values are numbers as they appear in the original JSON, without any additional notations.

To maintain clarity and consistency with the JSON format, the viewer should display these values as plain numbers without the n suffix.

[AnyRoad]

Hi,
As I understand (MDN) BigInt is not compatible with JSON anyway and you cannot accidently just got the BigInt value, it should be instantiated manully in the JavaScript code.
I think whether we should add the n suffix or not depends on the use case. If user wants to copy the output and use in the JS code it is better to add the suffix otherwise it might not work as expected (like this Issue #42 for instance)

[Assem-Uber]

I think whether we should add the n suffix or not depends on the use case

Agree that it can depends on the use case, Is there a way to support both use cases using the current library APIs or it is something to be added?

Basically my goal is to show big numbers with the same styles as numbers but without the suffix n.