The core's one JSON reader in its response mode, which every response body
goes through: a number literal of more than 15 characters (a Facebook id)
arrives as its exact text, exactly as json-bigint's storeAsString read it
before Node 22's reviver source text replaced it, a shorter number is the
number it reads as, and then every number under an id key (pk, user_id,
media_ids, …; isIdKey) is the text of the number, so an id is text
whatever its length. parseJson, parseNdjson, fromJsonText and the
screens' raw-node reader use this mode; parseJsonKeepingNumberLiterals is
the same reader in its literal mode.
The core's one JSON reader in its response mode, which every response body goes through: a number literal of more than 15 characters (a Facebook id) arrives as its exact text, exactly as json-bigint's
storeAsStringread it before Node 22's reviver source text replaced it, a shorter number is the number it reads as, and then every number under an id key (pk,user_id,media_ids, …;isIdKey) is the text of the number, so an id is text whatever its length.parseJson,parseNdjson,fromJsonTextand the screens' raw-node reader use this mode;parseJsonKeepingNumberLiteralsis the same reader in its literal mode.