npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

arraybuffer-xml-parser

v2.2.1

Published

Parse XML files contained in an array buffer

Readme

arraybuffer-xml-parser

NPM version build status Test coverage npm download

This code is based on a copy of fast-xml-parser.

The reason is that we wanted to parse large XML files (over 1Gb) and the current implementation of fast-xml-parser use as input a string. In the current implementation of javascript in V8 this limits the size to 512Mb.

In this code we parse directly a Uint8Array (or an ArrayBuffer) and the limit is now 4Gb.

Installation

$ npm i arraybuffer-xml-parser

Usage

XML to JSON

import { parse } from 'arraybuffer-xml-parser';

// in order to show an example we will encode the data to get the ArrayBuffer.

const encoder = new TextEncoder();
const xmlData = encoder.encode(
  `<rootNode><tag>value</tag><boolean>true</boolean><intTag>045</intTag><floatTag>65.34</floatTag></rootNode>`,
);

const object = parse(xmlData);

/*
object = {
  rootNode: {
    tag: 'value',
    boolean: true,
    intTag: 45,
    floatTag: 65.34,
  },
}
*/

By default text nodes and attribute values are dynamically typed, so 'true' becomes a boolean and '65.34' a number. Pass your own tagValueProcessor / attributeValueProcessor to keep the raw values.

Streaming a large XML

parseStream takes a web ReadableStream and yields one object per occurrence of lookupTagName, so a file larger than the available memory can be processed entry by entry.

import { open } from 'node:fs/promises';

import { parseStream } from 'arraybuffer-xml-parser';

const file = await open('medline.xml', 'r');

for await (const entry of parseStream(
  file.readableWebStream(),
  'PubmedArticle',
)) {
  console.log(entry);
}

Options

| Option | Description | Default value | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- | | trimValues | Remove ascii < 32 around string values of an attribute or node. | true | | attributesNodeName | (Valid name) Group all the attributes as properties of given name. | '' | | ignoreAttributes | Ignore attributes to be parsed. | false | | ignoreNameSpace | Remove namespace string from tag and attribute names. | false | | allowBooleanAttributes | A tag can have attributes without any value. | false | | textNodeName | Name of the property containing text nodes. | '#text' | | parseAttributesString | Parse the attributes of a tag. | true | | cdataTagName | If specified, parser parse CDATA as nested tag instead of adding it's value to parent tag. | false | | arrayMode | When false, a tag with single occurrence is parsed as an object but as an array in case of multiple occurences. When true, a tag will be parsed as an array always excluding leaf nodes. When strict, all the tags will be parsed as array only. When instance of RegEx, only tags will be parsed as array that match the regex. When function a tag name is passed to the callback that can be checked. | false | | tagNameProcessor | Callback to process tag names. Receives the tag name and the matching nodes. | (name) => name | | attributeNameProcessor | Callback to process attribute names. | prefix the name with $ | | tagValueProcessor | Process tag value during transformation. Like HTML decoding, word capitalization, etc. Receives the raw Uint8Array and the current node. | decode as UTF-8 and dynamically type the string | | attributeValueProcessor | Process attribute value during transformation. Like HTML decoding, word capitalization, etc. | dynamically type the string | | stopNodes | An array of tag names which are not required to be parsed. They are kept as Uint8Array. | [] |

parseStream accepts the same options plus:

| Option | Description | Default value | | ------------- | ----------------------------------------------- | ------------- | | maxEntrySize | Maximal size (in bytes) of a single entry. | 1e7 | | maxBufferSize | Maximal size (in bytes) of the internal buffer. | 2e8 |

API Documentation

License

MIT