Fixes large numbers parsed incorrectly when using JSON

[austenadler]

Description

The json-bigint was being used to parse the request body when JSON was used, but the library would convert large numbers to strings, and even larger numbers to strings in scientific notation.

This PR removes the json-bigint library, and always sends the user's json body without parsing through JSON or JSONbig (but it still passes through decomment()). This fixes #2202 and #2207

Old:

New:

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

[leoferreiralima]

Nice!

[benjibuiltit]

Would love to see this one merge in.

[ifsheldon]

I encountered this as well. But somehow this PR is still not merged.

[Its-treason]

Parsing the request to JSON is still required, because the axiosRequest (Returned as request here) is passed into runPreRequest and the body is used inside scripts. Where the body is expected to be an object (Instead of a string with JSON) when it's valid JSON.

I would suggest replacing json-bigint with lossless-json using a parse like this:

const { parse, LosslessNumber } = require('lossless-json');

parse(bodyData, null, (value) => {
  // This function will always be called, when lossless-json encounters a number
  // By Default this function only does "return new LosslessNumber(value);", but this sometimes auses problems
  // Convert the Lossless number into whatever fits best e.g. Number / BigInt
  return new LosslessNumber(value).valueOf();
});