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

@ismail-elkorchi/xml-parser

v0.2.0

Published

Namespace-aware XML parser with bounded resources and no runtime dependencies.

Readme

@ismail-elkorchi/xml-parser

A dependency-free XML 1.0 parser for Node.js, Deno, Bun, and modern browsers. It provides namespace-aware element and attribute trees, typed diagnostics, resource limits, serialization, queries, and simple structural validation.

The parser intentionally does not process DTDs. It supports predefined and numeric character references, but not document-defined entities, external entities, XSD, DOM APIs, canonical XML, or XML signatures.

Install

npm install @ismail-elkorchi/xml-parser
deno add jsr:@ismail-elkorchi/xml-parser

Parse XML

import { parseXml } from "@ismail-elkorchi/xml-parser";

const document = parseXml('<feed xmlns="urn:example"><entry id="1">Hello</entry></feed>');

if (document.errors.length > 0) {
  throw new Error(document.errors.map((error) => error.message).join("\n"));
}

console.log(document.root?.localName);     // feed
console.log(document.root?.namespaceURI); // urn:example

Malformed input produces a recovery tree and typed diagnostics. Always inspect document.errors before trusting or serializing the result.

Bytes and streams

parseXmlBytes() and parseXmlStream() accept UTF-8 only. The stream API enforces byte limits while reading, releases its reader on every path, and builds the tree after the complete stream has been decoded.

import { parseXmlStream } from "@ismail-elkorchi/xml-parser";

const response = await fetch("https://example.test/feed.xml");
if (!response.body) throw new Error("Response has no body");

const document = await parseXmlStream(response.body, {
  budgets: {
    maxInputBytes: 2_000_000,
    maxStreamBytes: 2_000_000,
    maxNodes: 25_000,
    maxDepth: 128,
    maxAttributesPerElement: 128,
    maxTextBytes: 1_000_000,
    maxErrors: 100,
    maxTimeMs: 2_000
  }
});

Exceeded limits throw XmlBudgetExceededError. Invalid options, arguments, profiles, and caller-constructed trees throw XmlConfigurationError. Invalid UTF-8 or a non-UTF-8 encoding declaration supplied to a byte API throws XmlDecodingError.

Query and serialize

import { listElementsByQName, parseXml, serializeXml } from "@ismail-elkorchi/xml-parser";

const document = parseXml("<catalog><book id=\"1\"/><book id=\"2\"/></catalog>");
if (document.errors.length > 0) throw new Error("Malformed XML");

console.log(listElementsByQName(document, "book").length); // 2
console.log(serializeXml(document));

The retained tree contains elements and text nodes. XML declarations, comments, processing instructions, DTDs, and the distinction between CDATA and ordinary text are not retained, so serialization is structural rather than a lexical round trip.

Documentation

Node.js 20, 22, and 24 are tested. Cross-runtime qualification covers Node.js, Deno, Bun, and Chromium. See the runnable examples for complete programs.