---
title: "Discussion on \"JSON.parse Source Text Access: Stop Losing Precision on Big IDs\" | Hashnode"
description: "Discussion on \"JSON.parse Source Text Access: Stop Losing Precision on Big IDs\". Your API returns an order ID of 9007199254740993. Your frontend logs 9007199254740992. Nobody touched it. JSON.parse quietly rounded it, because every JSON number becomes a JavaScript double, and doub"
url: "https://hashnode.com/posts/json-parse-source-text-access-stop-losing-precision-on-big-ids/6ae079a170a3906705961234"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [JSON.parse Source Text Access: Stop Losing Precision on Big IDs](https://grimicorn.hashnode.dev/json-parse-source-text-access-stop-losing-precision-on-big-ids?utm_source=hashnode&utm_medium=feed)

Your API returns an order ID of 9007199254740993. Your frontend logs 9007199254740992. Nobody touched it. JSON.parse quietly rounded it, because every JSON number becomes a JavaScript double, and doub

Oct 27 · 5 min read · grimicorn.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#web-apis](https://hashnode.com/tag/web-apis)
-   [#node](https://hashnode.com/tag/node)
-   [#json](https://hashnode.com/tag/json)

## Written by

[Dan Holloran](https://hashnode.com/@grimicorn)

@grimicorn · St. Louis, MO

  
[View profile](https://hashnode.com/@grimicorn)

Full-stack web developer since 2012 · Vue · React · Laravel · danholloran.me

Senior Full Stack Developer with 14+ years building performant, scalable web applications. Passionate about architecture, mentorship, and finding the right tool for the job.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
