NodeJsonFrag: a powerful combined tree-based and event-based parser for JSON

Typically, JSON is parsed by a tree-based parser unlike XML that can be parsed by a tree-based parser or an event-based parser. Event-based parsers are fast and have a low memory footprint, but a drawback is that it is cumbersome to write the required event handlers. Tree-based parsers make the code easier to write, to understand and to maintain but have a large memory footprint as a drawback. Sometimes, JSON is used for huge files such as database dumps that would be preferably parsed by event-based parsing, or so it would appear at a glance, because a tree-based parser cannot hold the whole parse tree in memory at the same time, if the file is huge.

How to install: NodeJsonFrag at NPM

NodeJsonFrag is available at NPM.

How to install:

npm install nodejsonfrag

Example application: customers in a major bank

Let us consider an example application: a listing of a customers in a major bank that has 30 million customers. The test file is in the following format:

{
  "customers": [
    {
      "id": 1,
      "name": "Clark Henson",
      "accountCount": 1,
      "totalBalance": 5085.96
    },
    {
      "id": 2,
      "name": "Elnora Ericson",
      "accountCount": 3,
      "totalBalance": 3910.11
    },
    ...
  ]
}

The example format requires about 100 bytes per customer plus customer name length. If we assume an average customer name is 15 characters long, the required storage is about 115 bytes per customer. For 30 million customers, this is 3.5 gigabytes. In the example, the file is read to the following structure:

{
  "id": <value>,
  "name": <value>,
  "accountCount": <value>,
  "totalBalance": <value>
};

Node jsonstream API

For XML, there is Simple API for XML (SAX). However, for JSON the usual parse methods read the whole data into memory at once, not supporting event-driven parsing. Thus, we provide Node jsonstream API to provide the possibility for event-driven parsing. It is faster and less memory-hungry than the "read all at once" parsing methods, but it is cumbersome.

A jsonstream-based parser is implemented here:

const nodejsonfrag = require('nodejsonfrag');
const fs = require('fs');

var context = [];
var c = {};
var cs = {};
handler = {
  start_dict: function(ctx, key)
  {
    context.push(key);
    if (context.length == 3 && context[0] == null && context[1] == "customers" && context[2] == null)
    {
      c = {};
    }
  },
  end_dict: function(ctx, key)
  {
    context.pop();
  },
  start_array: function(ctx, key)
  {
    context.push(key);
  },
  end_array: function(ctx, key)
  {
    context.pop();
  },
  handle_string: function(ctx, key, val)
  {
    if (key == "name")
    {
      c.name = val;
    }
  },
  handle_number: function(ctx, key, num, is_integer)
  {
    if (key == "id")
    {
      c.id = num;
      cs[String(c.id)] = c;
    }
    else if (key == "accountCount")
    {
      c.accountCount = num;
    }
    else if (key == "totalBalance")
    {
      c.totalBalance = num;
    }
  }
};

async function handleJson() {
  const ctx = nodejsonfrag.jsonstream_new(handler);
  const stream = fs.createReadStream('customers.json', {encoding: 'utf8'});
  for await (const chunk of stream)
  {
    nodejsonfrag.jsonstream_feed(ctx, chunk, 0, chunk.length, false);
  }
  nodejsonfrag.jsonstream_feed(ctx, '', 0, 0, true);
  console.log('STREAM HANDLED');
  console.log(cs);
}

handleJson();

It can be seen that the parser is quite cumbersome and the code to construct a customer is scattered to two different places. Yet it is fast and has a low memory footprint.

Parser with the new library

What if we could combine the benefits of the jsonstream-based approach with the benefits of the "read whole parse tree into memory" based approach? A parse tree fragment for a single customer dictionary is small enough to be kept in memory. This is what the new library is about. Here is the code to parse the customer file with the new library:

const nodejsonfrag = require('nodejsonfrag');
const fs = require('fs');

function my_start_dict(ctx, key)
{
        if (nodejsonfrag.jsonfrag_is(ctx, ["customers", null]))
        {
                nodejsonfrag.jsonfrag_start_fragment_collection(ctx);
        }
}
function my_end_dict(ctx, key, n)
{
        if (nodejsonfrag.jsonfrag_is(ctx, ["customers", null]))
        {
                console.log("id " + n.id);
                console.log("account count " + n.accountCount);
                console.log("total balance " + n.totalBalance);
                console.log("name " + n.name);
        }
}
const fraghandler = {
        'start_dict': my_start_dict,
        'end_dict': my_end_dict,
};

async function handleJson() {
  const ctx = nodejsonfrag.jsonfrag_new(fraghandler);
  const stream = fs.createReadStream('customers.json', {encoding: 'utf8'});
  for await (const chunk of stream)
  {
    nodejsonfrag.jsonstream_feed(ctx, chunk, 0, chunk.length, false);
  }
  nodejsonfrag.jsonstream_feed(ctx, '', 0, 0, true);
  console.log('STREAM HANDLED');
}

handleJson();

Note how the code is significantly more simple than for the event-based approach. Performance is close to the event-based approach, and memory consumption is essentially the same as for the event-based approach.

Of course, the new library supports getting the whole parse tree in memory:

const nodejsonfrag = require('nodejsonfrag');
const fs = require('fs');

buf = fs.readFileSync('customers.json', 'utf8');
console.log(nodejsonfrag.jsonstream_tree_parse(buf));

License

All of the material related to NodeJsonFrag is licensed under the following MIT license:

Copyright (C) 2026 Juha-Matti Tilli

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.