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

minimal-xml-parser

v0.1.0

Published

A simple XML parser with minimal capabilities

Readme

minimal-xml-parser

This is a simple XML parser. It does no validation beyond requiring the input to be well-formed.

It produces its output as a DOM Document Fragment. The user is required to supply the DOM implementation. Any implementation that conforms to DOM (Core) Level 1 may be used. minimal-dom is one such implementation.

Installation

Using npm:

npm install minimal-xml-parser

Example Usage

const Parser = require('minimal-xml-parser');
const Document = require('minimal-dom');

const xml = '<example><greeting>Hello, world!</greeting></example>'

let fragment = new Parser(xml, new Document()).parse();

console.log(String(fragment.firstChild.firstChild));

// outputs:
// <greeting>Hello, world!</greeting>

API

This module exports one class as its default:

Parser

The parser class provides the following methods:

It also provides the following property on the class:

new Parser(source, doc[, sourceName])

Parameters

  • source: String The XML document or fragment to parse
  • doc: Document An instance of a DOM Document that will be used to create the parser output.
  • sourceName: String (Optional) The name of the source (such as a file name) to use in any errors produced by the parser. Defaults to "<INPUT>".

Return Value

A new Parser instance.

Description

Creates a new instance of Parser. The document is not actually parsed until parse is called.

parser.parse()

Parameters

None.

Return Value

A DocumentFragment containing the parsed content.

Description

Parses the XML source supplied to the constructor. It creates a new DocumentFragment using the Document supplied to the constructor and adds all encountered elements and their content to that fragment. If any errors are encountered, this method throws an XMLSyntaxError.

Parser.XMLSyntaxError

The XMLSyntaxError property of the Parser class provides a reference to the XMLSyntaxError class:

const XMLSyntaxError = require('minimal-xml-parser').XMLSyntaxError;

try {
  callSomeRoutineThatParsesXML();
} catch (e) {
  if (e instanceof XMLSyntaxError)
    // error due to a parsing failure
  else
    // some other error
}

XMLSyntaxError

XMLSyntaxError is an Error class, instances of which are thrown when the parser encounters an error. Its message contains a full description of the error. It also provides the following properties:

  • sourceName: String The name of the source that produced the error.
  • line: Number The line number where the error occurred
  • column: Number The offset in characters on the line where the error occurred.
  • expected: String A token or description of what was expected next for valid XML.
  • actual: String The value that was encountered.