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

xml-reader

v2.4.3

Published

XML Reader and Parser

Downloads

384,216

Readme

XML Reader

Reads XML documents and emits JavaScript objects with a simple, easy to use structure.

Features

  • Small, fast and simple
  • Runs everywhere (browser, node.js, React Native, ServiceWorkers, WebWorkers...)
  • Event driven and synchronous API
  • Can process input piece-by-piece in a serial fashion
  • Stream mode (low memory usage)
  • Reads CDATA sections

Install

npm install --save xml-reader

Node structure

Objects emitted by the reader are trees where each node has the following structure:

interface XmlNode {
    name: string; // element name (empty for text nodes)
    type: string; // node type (element or text), see NodeType constants
    value: string; // value of a text node
    parent: XmlNode; // reference to parent node (null with parentNodes option disabled or root node)
    attributes: {[name: string]: string}; // map of attributes name => value
    children: XmlNode[];  // array of children nodes
}

Breaking changes in version 2

Added the tagPrefix option with a default value of 'tag:'. This way we avoid possible name collisions with the done event. To keep the old behavior, set it to an empty string.

Reading results

Check the xml-query package! It is very useful to read values from the structures returned by xml-reader.

Examples

Read document (event driven)

Basic example. Read and parse a XML document.

const XmlReader = require('xml-reader');
const reader = XmlReader.create();
const xml =
    `<?xml version="1.0" encoding="UTF-8"?>
    <message>
        <to>Alice</to>
        <from>Bob</from>
        <heading color="blue">Hello</heading>
        <body color="red">This is a demo!</body>
    </message>`;

reader.on('done', data => console.log(data));
reader.parse(xml);

/*
Console output:

{ name: 'message',
  type: 'element',
  children: [
    { name: 'to',
      type: 'element',
      children: [{ type: 'text', value: 'Alice' }]},
    { name: 'from',
      type: 'element',
      children: [{ type: 'text', value: 'Bob' }]},
    { name: 'heading',
      type: 'element',
      attributes: { color: 'blue' },
      children: [{ type: 'text', value: 'Hello' }]},
    { name: 'body',
      type: 'element',
      attributes: { color: 'red' },
      children: [{ type: 'text', value: 'This is a demo!' }]}]}

Note: empty values and references to parent nodes removed for brevity!
*/

Read document (synchronous)

This mode is only valid for reading complete documents (root node must be closed).

const XmlReader = require('xml-reader');

const xml = '<doc>Hello!</doc>';
const result = XmlReader.parseSync(xml/*, options*/);

Stream mode

In stream mode, nodes are removed from root as they are emitted. This way memory usage does not increases.

const XmlReader = require('xml-reader');

const reader = XmlReader.create({stream: true});
const xml =
    `<root>
        <item v=1/>
        <item v=2/>
        <item v=3/>
    </root>`;

reader.on('tag:item', (data) => console.log(data));
// {name: 'item', type: 'element', value: '', attributes: {v: '1'}, children: []}
// {name: 'item', type: 'element', value: '', attributes: {v: '2'}, children: []}
// {name: 'item', type: 'element', value: '', attributes: {v: '3'}, children: []}

reader.on('done', (data) => console.log(data.children.length));
// 0

reader.parse(xml);

You can also listen to all tags:

reader.on('tag', (name, data) => console.log(`received a ${name} tag:`, data));

Stream mode (chunked)

In this example we are calling multiple times to the parser. This is useful if your XML document is a stream that comes from a TCP socket or WebSocket (for example XMPP streams).

Simply feed the parser with the data as it arrives. As you can see, the result is exactly the same as the previous one.

const XmlReader = require('xml-reader');

const reader = XmlReader.create({stream: true});
const xml =
    `<root>
        <item v=1/>
        <item v=2/>
        <item v=3/>
    </root>`;

reader.on('tag:item', (data) => console.log(data));
// {name: 'item', type: 'element', value: '', attributes: {v: '1'}, children: []}
// {name: 'item', type: 'element', value: '', attributes: {v: '2'}, children: []}
// {name: 'item', type: 'element', value: '', attributes: {v: '3'}, children: []}

reader.on('done', (data) => console.log(data.children.length));
// 0

// Note that we are calling the parse function providing just one char each time
xml.split('').forEach(char => reader.parse(char));

Reset

Use the reset() method to reset the reader. This is useful if a stream gets interrupted and you want to start a new one or to use the same reader instance to parse multiple documents (just reset the reader between them).

Example:

const doc1 = '<document>...</document>';
const doc2 = '<document>...</document>';

reader.parse(doc1);

// when the document ends, the reader stops emitting events
reader.reset();

// now you can parse a new document
reader.parse(doc2);

Options

Default options are:

{
  stream: false,
  parentNodes: true,
  tagPrefix: 'tag:',
  doneEvent: 'done',
  emitTopLevelOnly: false,
}

parentNodes (boolean)

If true (default), each node of the AST has a parent node which point to its parent. If false the parent node is always null.

stream (boolean)

Enable or disable stream mode. In stream mode nodes are removed from root after being emitted. Default false. Ignored in parseSync;

doneEvent (string)

Default value is 'done'. This is the name of the event emitted when the root node is closed and the parse is done. Ignored in parseSync;

tagPrefix (string)

Default value is 'tag:'. The event driven API emits an event each time a tag is read. Use this option to set a name prefix. Ignored in parseSync;

emitTopLevelOnly (boolean)

Default value is false. When true, tag events are only emitted by top level nodes (direct children from root). This is useful for XMPP streams like XMPP where each top level child is a stanza.

For example, given the following XML stream:

<stream>
  <message from="alice" to="bob">
    <body>hello</body>
    <date>2016-10-06</date>
  </message>

  <message from="alice" to="bob">
    <body>bye</body>
    <date>2016-10-07</date>
  </message>

tags emitted with emitTopLevelOnly=false

body
date
message
body
date
message

tags emitted with emitTopLevelOnly=true

message
message

License

MIT