Support for BigInt numbers

[rangav]

Why this feature is better to be included in comment-json? Please describe the scenario
I like this library, Can you please support for bigInt number

Provide 1-2 code examples that the usage of the new feature:

var test = `{
  "data":2326453345646433546456576876786786,
  // data
  "sdfsf":"45455"
  // testing coments
}`

console.log(stringify(parse(test), null, 2))

// ------ output ----------
{
  "data": 2.3264533456464336e+33,
  // data
  "sdfsf": "45455"
  // testing coments
}

Are you willing to submit a pull request to implement this rule?
Please let me know which code part needs to be modified, I can try

[rangav]

Thanks @ambujsahu81 for the reply.

can you please share an example how to use reviver and replacer and also working with comments?

[rangav]

Thanks for sharing example.

[nikeee]

JSON.parse recently got an additional parameter for exactly these kinds of use-cases:
https://github.com/tc39/proposal-json-parse-with-source

const digitsToBigInt = (key, val, {source}) =>
  /^[0-9]+$/.test(source) ? BigInt(source) : val;

const bigIntToRawJSON = (key, val) =>
  typeof val === "bigint" ? JSON.rawJSON(String(val)) : val;

const tooBigForNumber = BigInt(Number.MAX_SAFE_INTEGER) + 2n;
JSON.parse(String(tooBigForNumber), digitsToBigInt) === tooBigForNumber;
// → true

const wayTooBig = BigInt("1" + "0".repeat(1000));
JSON.parse(String(wayTooBig), digitsToBigInt) === wayTooBig;
// → true

const embedded = JSON.stringify({ tooBigForNumber }, bigIntToRawJSON);
embedded === '{"tooBigForNumber":9007199254740993}';
// → true

Essentially, the reviver function now has a 3rd parameter that contains the string source.

The API in comment-json could probably be similar to this.

[kaelzhang]

JSON.parse recently got an additional parameter for exactly these kinds of use-cases: https://github.com/tc39/proposal-json-parse-with-source

const digitsToBigInt = (key, val, {source}) =>
/^[0-9]+$/.test(source) ? BigInt(source) : val;

const bigIntToRawJSON = (key, val) =>
typeof val === "bigint" ? JSON.rawJSON(String(val)) : val;

const tooBigForNumber = BigInt(Number.MAX_SAFE_INTEGER) + 2n;
JSON.parse(String(tooBigForNumber), digitsToBigInt) === tooBigForNumber;
// → true

const wayTooBig = BigInt("1" + "0".repeat(1000));
JSON.parse(String(wayTooBig), digitsToBigInt) === wayTooBig;
// → true

const embedded = JSON.stringify({ tooBigForNumber }, bigIntToRawJSON);
embedded === '{"tooBigForNumber":9007199254740993}';
// → true
Essentially, the reviver function now has a 3rd parameter that contains the string source.

The API in comment-json could probably be similar to this.

Awesome! Thanks for your input.

[kaelzhang]

Since the proposal is already in stage 3, I will start to implement the feature in the new branch

[kaelzhang]

Landed in 4.4.0

Here

I just changed several lines of code in parse.js