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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@borgar/simple-xml

v2.0.1

Published

Overly simplistic (but fast) XML parser

Downloads

1,080

Readme

Overly simplistic XML parser

This is an overly simplistic non-validating XML parser with utilities. It will indiscriminately parse most well-formed XML documents that don't try to do anything clever.

The purpose of this library to allow easy parsing and consuming XML files. Does the world really need it? No, probably not. But all the other available packages the author tested were either a massive overkill or failed to parse fairly simplistic XML correctly. So here we are.

There are some limitations:

  • Comments are discarded.
  • Processing instructions are discarded.
  • Namespace prefixes are preserved but otherwise ignored.
  • Doctypes are discarded.
  • Nested doctypes are not supported and will cause errors.
  • Nodes have a limited interface.
  • Made for a node.js environment with no browser build provided.

But on the upside:

  • Built in selector engine.
  • No dependencies.

Installing

The usual:

$ npm i @borgar/simple-xml

Parsing XML

import { parseXML } from '@borgar/simple-xml';

const dom = parseXML('<root><node>Lorem ipsum</node></root>');
console.log(dom.getElementsByTagName('node').textContent);

The parse function accepts two arguments, the first is an XML source. The second is an options object. There are two options:

Allow normally forbidden unquoted attributes with laxAttr:

parseXML('<root><node foo=bar /></root>', { laxAttr: true });

Allow normally forbidden "rootless" documents with emptyDoc:

parseXML('', { emptyDoc: true });

As well as a parse method, the package exports Node classes: Node, Element, Document, TextNode, and CDataNode. They are pretty much what you expect but with an incomplete or altered set of DOM API functions.

See the API documentation.

Nodes have the following methods and properties

Name & identity

  • .nodeName An uppercase tag name. (BAR in the case of <foo:bar>)

  • .tagName A case preserved tag (bar in the case of <foo:bar>)

  • .nodeType A node type number (e.g. Element.ELEMENT_NODE === 1)

  • .ns A namespace identifier (foo in the case of <foo:bar>)

  • .fullName A full tag name with identifier (foo:bar in the case of <foo:bar>)

Attributes

  • .getAttribute( attrName )
  • .setAttribute( attrName, attrValue )
  • .hasAttribute( attrName )
  • .removeAttribute( attrName )

Attributes are not stored as attribute nodes in a list, but rather they are a simple { name: value } style object on the node.

Tree & traversal

  • .appendChild( Node ) Inserts a new node as the last child of a parent. If a node already has a parent, it is removed from that parent when inserted in the target.

  • .children Emits an array of direct child nodes that are of type Element.

  • .parentNode A direct reference to the node's container.

  • .childNodes An array of all direct child nodes.

  • .textContent Emits the text content of the target's subtree.

    Text is preserved as-is in the tree but whitespace is cleaned (unless xml:space dictates otherwise) when using .textContent.

  • .getElementsByTagName( tagName ) Lists all Elements in the target's subtree, traversal order, that have .tagName equal to the argument. Function is case-sensitive.

  • .querySelectorAll( cssSelector ) Lists all Elements in the target's subtree, traversal order, that match the supplied CSS selector. Function should be case-sensitive but may be case insensitive for some.

  • .toJS() Returns the target node's subtree in a JsonML-like structure.

Roughly, if you supply this:

<x:tag foo="bar">Text content</x:tag>

It will parse to a document which has a .root node looking roughly like this:

{
  nodeType: 1,
  nodeName: 'TAG',
  ns: 'x',
  tagName: 'tag',
  fullName: 'x:tag',
  attr: { 'foo': 'bar' }
  parentNode: null,
  childNodes = [
    {
      nodeName: '#text',
      nodeType: 3,
      value: 'Text content',
      parentNode: {...},
    }
  ]
}