RIrictic·Oct 23, 2025
For anyone else following along, see https://github.com/rictic/jsonriver/issues/39
In JSON River – Parse JSON incrementally as it streams inrictic
jsonriver
TypeScript2025–2025
rictic / jsonriver
jsonriver
A simple, fast streaming JSON parser built on standards.
2Distinct people
5Mentions
0Explicit recommenders
1.2KGitHub stars
What to know before exploring
What it is
A simple, fast streaming JSON parser built on standards.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week5 dated mentions
Observed mentions: 2025-06-01 16:40:46 UTC to 2025-10-23 02:01:19 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| May 26 | 2025-05-26 00:00:00 UTC | 2025-06-02 00:00:00 UTC | 1 | 0 | 1 |
| Jun 2 | 2025-06-02 00:00:00 UTC | 2025-06-09 00:00:00 UTC | 1 | 0 | 1 |
| Jun 9 | 2025-06-09 00:00:00 UTC | 2025-06-16 00:00:00 UTC | 0 | 0 | 0 |
| Jun 16 | 2025-06-16 00:00:00 UTC | 2025-06-23 00:00:00 UTC | 0 | 0 | 0 |
| Jun 23 | 2025-06-23 00:00:00 UTC | 2025-06-30 00:00:00 UTC | 0 | 0 | 0 |
| Jun 30 | 2025-06-30 00:00:00 UTC | 2025-07-07 00:00:00 UTC | 0 | 0 | 0 |
| Jul 7 | 2025-07-07 00:00:00 UTC | 2025-07-14 00:00:00 UTC | 0 | 0 | 0 |
| Jul 14 | 2025-07-14 00:00:00 UTC | 2025-07-21 00:00:00 UTC | 0 | 0 | 0 |
| Jul 21 | 2025-07-21 00:00:00 UTC | 2025-07-28 00:00:00 UTC | 0 | 0 | 0 |
| Jul 28 | 2025-07-28 00:00:00 UTC | 2025-08-04 00:00:00 UTC | 0 | 0 | 0 |
| Aug 4 | 2025-08-04 00:00:00 UTC | 2025-08-11 00:00:00 UTC | 0 | 0 | 0 |
| Aug 11 | 2025-08-11 00:00:00 UTC | 2025-08-18 00:00:00 UTC | 0 | 0 | 0 |
| Aug 18 | 2025-08-18 00:00:00 UTC | 2025-08-25 00:00:00 UTC | 0 | 0 | 0 |
| Aug 25 | 2025-08-25 00:00:00 UTC | 2025-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 1 | 2025-09-01 00:00:00 UTC | 2025-09-08 00:00:00 UTC | 0 | 0 | 0 |
| Sep 8 | 2025-09-08 00:00:00 UTC | 2025-09-15 00:00:00 UTC | 0 | 0 | 0 |
| Sep 15 | 2025-09-15 00:00:00 UTC | 2025-09-22 00:00:00 UTC | 0 | 0 | 0 |
| Sep 22 | 2025-09-22 00:00:00 UTC | 2025-09-29 00:00:00 UTC | 0 | 0 | 0 |
| Sep 29 | 2025-09-29 00:00:00 UTC | 2025-10-06 00:00:00 UTC | 0 | 0 | 0 |
| Oct 6 | 2025-10-06 00:00:00 UTC | 2025-10-13 00:00:00 UTC | 1 | 1 | 0 |
| Oct 13 | 2025-10-13 00:00:00 UTC | 2025-10-20 00:00:00 UTC | 1 | 0 | 1 |
| Oct 20 | 2025-10-20 00:00:00 UTC | 2025-10-27 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesYeah, getting numbers correct was one of the trickier wrinkles in the project. https://github.com/rictic/jsonriver/blob/5515be978bb564e9bdc...
In JSON River – Parse JSON incrementally as it streams inJSON River – Parse JSON incrementally as it streams in
238 points · Open discussionGood question. jsonriver is well optimized, exhaustively tested (tens of thousands of test cases), and provides a number of potentially useful invariants[0] about its parsing.
jsonriver's performance comes primarily from simplicity, and doing as little work per character as we can. Repeatedly reparsing from scratch on the other hand gets expensive quick, your parse time is quadratic in the length of the string to parse.
[0] https://github.com/rictic/jsonriver?tab=readme-ov-file#invar...
In Progressive JSONIf you've got some client side code and want to parse and render JSON progressively, try out jsonriver: https://github.com/rictic/jsonriver
Very simple API, takes a stream of string chunks and returns a stream of increasingly complete values. Helpful for parsing large JSON, and JSON being emitted by LLMs.
Extensively tested and performance optimized. Guaranteed that the final value emitted is identical to passing the entire string through JSON.parse.
In Progressive JSON