Home/Answers/Big integers
JSON→TS / Big integers

Common Big integers Mistakes

The most common Big integers mistakes are overwriting originals, ignoring format/quality and not checking the output.

Updated 2026-10-31About 3 minLocal test
Quick answer

The most common Big integers mistakes are overwriting originals, ignoring format/quality and not checking the output. JSON numbers are IEEE754; large IDs may lose precision, so use strings.

Why it matters

These mistakes cause irreversible data or quality loss.

Above 2^53 is unsafe.

Step by step

  1. Start with real/complete JSON covering optional fields and empty arrays.
  2. Check array elements, null/optional and nested objects.
  3. Set the root name and copy into the project.
  4. Add Zod/Valibot runtime validation for production.
  5. Add contract tests/versioning for API changes.

Common mistakes

  • Treating a sample as a complete schema, missing optional/empty arrays.
  • Trusting generated any/null unions as-is.
  • Forgetting quotes for property names with spaces/Chinese.
  • Skipping runtime validation after generation.

Checklist

  • Sample covers optional/empty arrays/null.
  • Array object fields merged.
  • Property/root names valid.
  • Runtime validation added.
  • API contract/version considered.

Key facts

  • Above 2^53 is unsafe.
  • Backends should return strings.

FAQ

What are common Big integers mistakes?

The most common Big integers mistakes are overwriting originals, ignoring format/quality and not checking the output. JSON numbers are IEEE754; large IDs may lose precision, so use strings.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: MDN Number