JSON→TS / JSON

How to Choose JSON

Choose JSON by use case and compatibility first, specs second; test locally when possible.

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

Choose JSON by use case and compatibility first, specs second; test locally when possible. JSON has only objects/arrays/strings/numbers/booleans/null, no dates/undefined.

Why it matters

Stacked specs do not guarantee fit for your use case.

Dates are usually ISO strings.

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

  • Dates are usually ISO strings.
  • Large integers may lose precision.

FAQ

How do I choose JSON?

Choose JSON by use case and compatibility first, specs second; test locally when possible. JSON has only objects/arrays/strings/numbers/booleans/null, no dates/undefined.

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 JSON