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

saxy

v0.7.3

Published

Fast and lightweight event-driven XML parser in pure TypeScript, forked from Saxophone

Downloads

123

Readme

Saxy

Fast and lightweight event-driven streaming XML parser in pure TypeScript.

npm version npm downloads build status coverage

Saxy is forked from Saxophone version 0.7.2 and converted to TypeScript, so most credits go to the original author, Mattéo Delabre. Besides converting it to TypeScript, so you have proper typings when using it, it also includes several unmerged pull requests Marcellino Ornelas and Philip Otto, i.e. the parser is a Transform stream instead of a Writeable stream, so you can pipe information through, and testing on Node 16.

It is inspired by SAX parsers such as sax-js and EasySax: unlike most XML parsers, it does not create a Document Object Model (DOM) tree as a result of parsing documents. Instead, it emits events for each tag or text node encountered as the parsing goes on. This means that Saxy has a really low memory footprint and can easily parse large documents.

The parser does not keep track of the document state while parsing and, in particular, does not check whether the document is well-formed or valid, making it super-fast (see benchmarks below).

This library is best suited when you need to extract simple data out of an XML document that you know is well-formed. The parser will not report precise errors in case of syntax problems. An example would be reading data from an API endpoint.

Installation

This library works both in Node.JS ≥6.0 and recent browsers. To install, use either one of below commands:

npm install --save saxy
pnpm add saxy
yarn add saxy

Benchmark

This benchmark compares the performance of four of the most popular SAX parsers against Saxy’s performance while parsing a 21 KB document. Below are the results when run on a Intel® Core™ i7-7500U processor (2.70GHz, 2 physical cores with 2 logical cores each).

| Library | Version | Operations per second (higher is better) | | ------------------ | ------: | ---------------------------------------: | | Saxy | 0.5.0 | 6,840 ±1.48% | | EasySax | 0.3.2 | 7,354 ±1.16% | | node-expat | 2.3.17 | 1,251 ±0.60% | | libxmljs.SaxParser | 0.19.5 | 1,007 ±0.81% | | sax-js | 1.2.4 | 982 ±1.50% |

To run the benchmark by yourself, use the following commands:

git clone https://github.com/matteodelabre/saxy.git
cd saxy
npm install
npm install --no-save easysax node-expat libxmljs sax
npm run benchmark

Tests and coverage

To run tests and check coverage, use the following commands:

git clone https://github.com/matteodelabre/saxy.git
cd saxy
npm install
npm test
npm run coverage

Examples

Simple example

import { Saxy } from 'Saxy';
const parser = new Saxy();

// Called whenever an opening tag is found in the document,
// such as <example id="1" /> - see below for a list of events
parser.on('tagopen', tag => {
  console.log(
    `Open tag "${tag.name}" with attributes: ${JSON.stringify(Saxy.parseAttrs(tag.attrs))}.`
  );
});

// Called when we are done parsing the document
parser.on('finish', () => {
  console.log('Parsing finished.');
});

// Triggers parsing - remember to set up listeners before
// calling this method
parser.parse('<root><example id="1" /><example id="2" /></root>');

Output:

Open tag "root" with attributes: {}.
Open tag "example" with attributes: {"id":"1"}.
Open tag "example" with attributes: {"id":"2"}.
Parsing finished.

Streaming example

Same example as above but with Streams.

import { Saxy } from 'saxy';
const parser = new Saxy();

// Called whenever an opening tag is found in the document,
// such as <example id="1" /> - see below for a list of events
parser.on('tagopen', tag => {
  console.log(
    `Open tag "${tag.name}" with attributes: ${JSON.stringify(Saxy.parseAttrs(tag.attrs))}.`
  );
});

// Called when we are done parsing the document
parser.on('finish', () => {
  console.log('Parsing finished.');
});

// stdin is '<root><example id="1" /><example id="2" /></root>'
process.stdin.setEncoding('utf8');
process.stdin.pipe(parser);

Output:

Open tag "root" with attributes: {}.
Open tag "example" with attributes: {"id":"1"}.
Open tag "example" with attributes: {"id":"2"}.
Parsing finished.

Transform Stream

Saxy can now be used as a transform stream to send the parsed XML to another stream. Saxy works to keep low memory so it doesn't save any of the XML internally but uses events to fire certain data. So how do you tell the parser to send data to the next stream? The way to send data to another stream is to use the parser.push() method.

Example:

<root>
  <page>Hey this is some text</page>
</root>
import { createReadStream } from 'fs';
import { Saxy } from 'saxy';

const parser = new Saxy();

parser.on('text', function(data) {
  // Get the text from saxy
  const text = data.contents;

  // Send the data to the next stream;
  parser.push(text);
});

createReadStream('file.xml')
  .pipe(parser)
  .pipe(process.stdout); // Hey this is some text

Documentation

new Saxy()

Creates a new Saxy parser instance. This object is a transform stream that will emit an event for each tag or node parsed from the incoming data. See the list of events below.

Saxy#on(), Saxy#removeListener()

Manage event listeners just like with any other event emitter. Saxy inherits from all EventEmitter methods. See the relevant Node documentation.

Saxy#parse(xml)

Trigger the parsing of a whole document. This method will fire registered listeners, so you need to set them up before calling it. This is equivalent to writing xml to the stream and closing it.

Note: the parser cannot be reused afterwards, you need to create a new instance.

Arguments:

  • xml is an UTF-8 string or a Buffer containing the XML that you want to parse.

This method returns the parser instance.

Saxy#write(xml)

Parse a chunk of a XML document. This method will fire registered listeners so you need to set them up before calling it.

Note: an event is emitted for a tag or a node only when it has been closed. If the chunk starts a tag but does not close it, the tag will not be reported until it is closed by a later chunk.

Arguments:

  • xml is an UTF-8 string or a Buffer containing a chunk of the XML that you want to parse.

Saxy#end(xml = "")

Write an optional last chunk then close the stream. After the stream is closed, a final finish event is emitted and no other event will be emitted afterwards. No more data may be written into the stream after closing it.

Arguments:

  • xml is an UTF-8 string or a Buffer containing a chunk of the XML that you want to parse.

Saxy.parseAttrs(attrs)

Parse a string list of XML attributes, as produced by the main parsing algorithm. This is not done automatically because it may not be required for every tag and it takes some time.

The result is an object associating the attribute names (as object keys) to their attribute values (as object values).

Saxy.parseEntities(text)

Parses a piece of XML text and expands all XML entities inside it to the character they represent. Just like attributes, this is not parsed automatically because it takes some time.

This ignores invalid entities, including unrecognized ones, leaving them as-is.

Events

tagopen

Emitted when an opening tag is parsed. This encompasses both regular tags and self-closing tags. An object is passed with the following data:

  • name: name of the parsed tag.
  • attrs: attributes of the tag (as a string). To parse this string, use Saxy.parseAttrs.
  • isSelfClosing: true if the tag is self-closing.

tagclose

Emitted when a closing tag is parsed. An object containing the name of the tag is passed.

processinginstruction

Emitted when a processing instruction (such as <? contents ?>) is parsed. An object with the contents of the processing instruction is passed.

text

Emitted when a text node between two tags is parsed. An object with the contents of the text node is passed. You might need to expand XML entities inside the contents of the text node, using Saxy.parseEntities.

cdata

Emitted when a CDATA section (such as <![CDATA[ contents ]]>) is parsed. An object with the contents of the CDATA section is passed.

comment

Emitted when a comment (such as <!-- contents -->) is parsed. An object with the contents of the comment is passed.

error

Emitted when a parsing error is encountered while reading the XML stream such that the rest of the XML cannot be correctly interpreted:

  • when a DOCTYPE node is found (not supported yet);
  • when a comment node contains the -- sequence;
  • when opening and closing tags are mismatched or missing;
  • when a tag name starts with white space;
  • when nodes are unclosed (missing their final >).

Because this library's goal is not to provide accurate error reports, the passed error will only contain a short description of the syntax error (without giving the position, for example).

finish

Emitted after all events, without arguments.

Contributions

This is free and open source software. All contributions (even small ones) are welcome. Check out the contribution guide to get started!

Thanks to Norman Rzepka for implementing the streaming API and the check for opening and closing tags mismatch.

License

Released under the MIT license. See the full license text.