The large ints thing is because people forget that numerics in Javascript are all officially floating point. The optimisers might often see that they can use real integers for performance, but you can't depend on that so have to assume it isn't happening.
Integer numbers are accurate up to 2^53-1 (and down to -2^53) as the IEEE754 double precision type is used, which is sufficient for a majority of tasks, but obviously not all.
Native BigInt (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...) is widely supported these days (has been since late 2020 IIRC, or early 2023 if you waited for LTS releases without the feature to reach EOL) but is not yet widely used (many don't seem to know it is there, or assume it isn't widely supported, or are concerned about performance). Performance isn't usually bad (about 60% or the basis Number type last time I compared) but there are other issues with JSON or with many libraries only supporting Number not BigInt.
Integer numbers are accurate up to 2^53-1 (and down to -2^53) as the IEEE754 double precision type is used, which is sufficient for a majority of tasks, but obviously not all.
Native BigInt (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...) is widely supported these days (has been since late 2020 IIRC, or early 2023 if you waited for LTS releases without the feature to reach EOL) but is not yet widely used (many don't seem to know it is there, or assume it isn't widely supported, or are concerned about performance). Performance isn't usually bad (about 60% or the basis Number type last time I compared) but there are other issues with JSON or with many libraries only supporting Number not BigInt.