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

stricter-htmlparser2

v3.9.6

Published

Fast & forgiving HTML/XML/RSS parser with stricter attribute parsing rules.

Downloads

4,522

Readme

stricter-htmlparser2

NPM version Downloads Build Status Coverage

A forgiving HTML/XML/RSS parser. The parser can handle streams and provides a callback interface.

Installation

npm install 'stricter-htmlparser2'

A live demo of htmlparser2 is available here.

Differences to htmlparser2

  1. Attribute value without quote wrapped is not allowed.

    <foo name=value />
    
    // output
    {
    	attribs: {
    		name: "",
    		value: ""
    	}
    }
  2. """ is allowed in attribute value.

    <foo name="hello \"world" />
    
    // output
    {
    	attribs: {
    		name: "hello \\"world"
    	}
    }
  3. Record attributes key in a object that value is wrapped by single quote. The object is passed to onopentag method of parser's domhandler through the third argument.

    <foo name='{{flag ? "true" : "false"}}' title="title" class='hidden'> </foo>
    
    // The third argument passed to onopentag:
    {
    	name: true,
    	class: true
    }

    // If used with x-domhandler which is exported by this module, the parse result is like this:

    {
    	type: "tag",
    	name: "foo",
    	attribs: {
    		name: "{{flag ? \"true\" : \"false\"}}",
    		title: "title",
    		class: "hidden"
    	},
    	singleQuoteAttribs: {
    		name: true,
    		class: true
    	},
    	selfClose: false
    }
  4. Add selfClose flag to parsed node element.

    Input:

    <foo name='{{flag ? "true" : "false"}}' title="title" class='hidden' />

    Parser code:

    const {Parser, DomHandler} = require('stricter-htmlparser2');
    
    const parser = new Parser(new DomHandler(), {}).end(inputStr);

    Output

    {
    	type: "tag",
    	name: "foo",
    	attribs: {
    		name: "{{flag ? \"true\" : \"false\"}}",
    		title: "title",
    		class: "hidden"
    	},
    	singleQuoteAttribs: {
    		name: true,
    		class: true
    	},
    	selfClose: true
    }

Usage

var htmlparser = require("stricter-htmlparser2");
var parser = new htmlparser.Parser({
	onopentag: function(name, attribs){
		if(name === "script" && attribs.type === "text/javascript"){
			console.log("JS! Hooray!");
		}
	},
	ontext: function(text){
		console.log("-->", text);
	},
	onclosetag: function(tagname){
		if(tagname === "script"){
			console.log("That's it?!");
		}
	}
}, {decodeEntities: true});
parser.write("Xyz <script type='text/javascript'>var foo = '<<bar>>';</ script>");
parser.end();

Output (simplified):

--> Xyz
JS! Hooray!
--> var foo = '<<bar>>';
That's it?!

Documentation

Read more about the parser and its options in the wiki.

Get a DOM

The DomHandler (known as DefaultHandler in the original htmlparser module) produces a DOM (document object model) that can be manipulated using the DomUtils helper.

The DomHandler, while still bundled with this module, was moved to its own module. Have a look at it for further information.

Parsing RSS/RDF/Atom Feeds

new htmlparser.FeedHandler(function(<error> error, <object> feed){
    ...
});

Note: While the provided feed handler works for most feeds, you might want to use danmactough/node-feedparser, which is much better tested and actively maintained.

Performance

After having some artificial benchmarks for some time, @AndreasMadsen published his htmlparser-benchmark, which benchmarks HTML parses based on real-world websites.

At the time of writing, the latest versions of all supported parsers show the following performance characteristics on Travis CI (please note that Travis doesn't guarantee equal conditions for all tests):

gumbo-parser   : 34.9208 ms/file ± 21.4238
html-parser    : 24.8224 ms/file ± 15.8703
html5          : 419.597 ms/file ± 264.265
htmlparser     : 60.0722 ms/file ± 384.844
htmlparser2-dom: 12.0749 ms/file ± 6.49474
htmlparser2    : 7.49130 ms/file ± 5.74368
hubbub         : 30.4980 ms/file ± 16.4682
libxmljs       : 14.1338 ms/file ± 18.6541
parse5         : 22.0439 ms/file ± 15.3743
sax            : 49.6513 ms/file ± 26.6032

How does this module differ from node-htmlparser?

This is a fork of the htmlparser module. The main difference is that this is intended to be used only with node (it runs on other platforms using browserify). htmlparser2 was rewritten multiple times and, while it maintains an API that's compatible with htmlparser in most cases, the projects don't share any code anymore.

The parser now provides a callback interface close to sax.js (originally targeted at readabilitySAX). As a result, old handlers won't work anymore.

The DefaultHandler and the RssHandler were renamed to clarify their purpose (to DomHandler and FeedHandler). The old names are still available when requiring htmlparser2, your code should work as expected.