htmlparser2 vs cheerio vs jsdom vs parse5
HTML 解析和操作库
htmlparser2cheeriojsdomparse5类似的npm包:

HTML 解析和操作库

这些库用于在Node.js环境中解析和操作HTML文档。它们各自提供了不同的功能和设计理念,适用于不同的使用场景。选择合适的库可以提高开发效率和代码的可维护性。

npm下载趋势

3 年

GitHub Stars 排名

统计详情

npm包名称
下载量
Stars
大小
Issues
发布时间
License
htmlparser294,233,0374,788235 kB135 个月前MIT
cheerio29,191,69030,4681.01 MB567 个月前MIT
jsdom021,6597.09 MB4031 个月前MIT
parse503,925337 kB404 个月前MIT

功能对比: htmlparser2 vs cheerio vs jsdom vs parse5

解析能力

  • htmlparser2:

    htmlparser2是一个高性能的HTML解析器,能够处理不规范的HTML。它支持流式解析,可以逐步读取和解析HTML文档,适合处理大文件。

  • cheerio:

    Cheerio是一个快速、灵活的库,专注于解析和操作HTML。它能够处理简单的HTML文档,并提供类似jQuery的选择器和操作方法,非常适合网页抓取和数据提取。

  • jsdom:

    jsdom提供了一个完整的DOM实现,能够模拟浏览器的行为。它支持大部分浏览器API,适合需要进行复杂DOM操作的场景。

  • parse5:

    parse5是一个符合HTML5标准的解析器,能够处理复杂的HTML结构。它提供了灵活的API,适合需要深度解析和操作HTML的应用。

性能

  • htmlparser2:

    htmlparser2以其高性能著称,能够快速解析大文件。它的流式解析特性使得在处理大型HTML文档时性能优越。

  • cheerio:

    Cheerio的性能相对较高,适合快速解析和操作小型HTML文档。由于其轻量级的特性,处理速度较快,但在处理大型文档时可能会受到限制。

  • jsdom:

    jsdom的性能相对较低,因为它模拟了完整的浏览器环境,适合进行复杂的DOM操作,但在性能上可能不如其他库。

  • parse5:

    parse5在解析复杂HTML时表现良好,能够处理各种边缘案例,但在性能上可能不如htmlparser2。

API 设计

  • htmlparser2:

    htmlparser2的API设计注重性能和灵活性,支持流式解析和事件驱动的处理方式,适合需要高效解析的场景。

  • cheerio:

    Cheerio的API设计灵活且易于使用,提供了类似jQuery的选择器和操作方法,使得开发者能够快速上手并进行DOM操作。

  • jsdom:

    jsdom的API设计旨在模拟浏览器环境,提供了丰富的DOM操作接口,适合需要进行复杂测试的场景。

  • parse5:

    parse5的API设计符合HTML5标准,能够处理复杂的HTML结构,适合需要深度解析和操作的应用。

使用场景

  • htmlparser2:

    htmlparser2适合处理大文件和不规范的HTML,特别是在需要逐步解析的场景中表现优异。

  • cheerio:

    Cheerio适合用于网页抓取、数据提取和简单的HTML操作,特别是在需要快速解析小型文档时。

  • jsdom:

    jsdom适合需要模拟浏览器环境的测试和开发场景,特别是在需要使用浏览器API时。

  • parse5:

    parse5适合需要处理复杂HTML文档的应用,特别是在需要符合HTML5标准的场景中。

学习曲线

  • htmlparser2:

    htmlparser2的学习曲线相对较陡,特别是在使用流式解析时,开发者需要理解事件驱动的编程模型。

  • cheerio:

    Cheerio的学习曲线较平缓,开发者可以快速上手,尤其是熟悉jQuery的开发者。

  • jsdom:

    jsdom的学习曲线较为平缓,尤其是对于熟悉浏览器API的开发者,但其完整的DOM实现可能需要更多的学习和理解。

  • parse5:

    parse5的学习曲线适中,开发者需要理解HTML5标准和解析的细节,但其灵活的API设计使得上手相对容易。

如何选择: htmlparser2 vs cheerio vs jsdom vs parse5

  • htmlparser2:

    选择htmlparser2如果你需要一个高性能的HTML解析器,能够处理不规范的HTML。它支持流式解析,适合处理大文件或需要逐步解析的场景。

  • cheerio:

    选择Cheerio如果你需要一个轻量级的库来快速解析和操作HTML,尤其是在进行网页抓取时。它提供了类似于jQuery的API,使得操作DOM变得简单直观。

  • jsdom:

    选择jsdom如果你需要一个完整的DOM实现,能够模拟浏览器环境。它适合需要进行DOM操作和测试的场景,尤其是需要使用浏览器API的情况。

  • parse5:

    选择parse5如果你需要一个符合HTML5标准的解析器,能够处理复杂的HTML文档。它提供了灵活的API,适合需要深度解析和操作HTML的应用。

htmlparser2的README

htmlparser2

NPM version Downloads Node.js CI Coverage

The fast & forgiving HTML/XML parser.

htmlparser2 is the fastest HTML parser, and takes some shortcuts to get there. If you need strict HTML spec compliance, have a look at parse5.

Installation

npm install htmlparser2

A live demo of htmlparser2 is available on AST Explorer.

Ecosystem

NameDescription
htmlparser2Fast & forgiving HTML/XML parser
domhandlerHandler for htmlparser2 that turns documents into a DOM
domutilsUtilities for working with domhandler's DOM
css-selectCSS selector engine, compatible with domhandler's DOM
cheerioThe jQuery API for domhandler's DOM
dom-serializerSerializer for domhandler's DOM

Usage

htmlparser2 itself provides a callback interface that allows consumption of documents with minimal allocations. For a more ergonomic experience, read Getting a DOM below.

import * as htmlparser2 from "htmlparser2";

const parser = new htmlparser2.Parser({
    onopentag(name, attributes) {
        /*
         * This fires when a new tag is opened.
         *
         * If you don't need an aggregated `attributes` object,
         * have a look at the `onopentagname` and `onattribute` events.
         */
        if (name === "script" && attributes.type === "text/javascript") {
            console.log("JS! Hooray!");
        }
    },
    ontext(text) {
        /*
         * Fires whenever a section of text was processed.
         *
         * Note that this can fire at any point within text and you might
         * have to stitch together multiple pieces.
         */
        console.log("-->", text);
    },
    onclosetag(tagname) {
        /*
         * Fires when a tag is closed.
         *
         * You can rely on this event only firing when you have received an
         * equivalent opening tag before. Closing tags without corresponding
         * opening tags will be ignored.
         */
        if (tagname === "script") {
            console.log("That's it?!");
        }
    },
});
parser.write(
    "Xyz <script type='text/javascript'>const foo = '<<bar>>';</script>",
);
parser.end();

Output (with multiple text events combined):

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

Parser events

All callbacks are optional. The handler object you pass to Parser may implement any subset of these:

EventDescription
onopentag(name, attribs, isImplied)Opening tag. attribs is an object mapping attribute names to values. isImplied is true when the tag was opened implicitly (HTML mode only).
onopentagname(name)Emitted for the tag name as soon as it is available (before attributes are parsed).
onattribute(name, value, quote)Attribute. quote is " / ' / null (unquoted) / undefined (no value, e.g. disabled).
onclosetag(name, isImplied)Closing tag. isImplied is true when the tag was closed implicitly (HTML mode only).
ontext(data)Text content. May fire multiple times for a single text node.
oncomment(data)Comment (content between <!-- and -->).
oncdatastart()Opening of a CDATA section (<![CDATA[).
oncdataend()End of a CDATA section (]]>).
onprocessinginstruction(name, data)Processing instruction (e.g. <?xml ...?>).
oncommentend()Fires after a comment has ended.
onparserinit(parser)Fires when the parser is initialized or reset.
onreset()Fires when parser.reset() is called.
onend()Fires when parsing is complete.
onerror(error)Fires on error.

Parser options

OptionTypeDefaultDescription
xmlModebooleanfalseTreat the document as XML. This affects entity decoding, self-closing tags, CDATA handling, and more. Set this to true for XML, RSS, Atom and RDF feeds.
decodeEntitiesbooleantrueDecode HTML entities (e.g. &amp; -> &).
lowerCaseTagsboolean!xmlModeLowercase tag names.
lowerCaseAttributeNamesboolean!xmlModeLowercase attribute names.
recognizeSelfClosingbooleanxmlModeRecognize self-closing tags (e.g. <br/>). Always enabled in xmlMode.
recognizeCDATAbooleanxmlModeRecognize CDATA sections as text. Always enabled in xmlMode.

Usage with streams

While the Parser interface closely resembles Node.js streams, it's not a 100% match. Use the WritableStream interface to process a streaming input:

import { WritableStream } from "htmlparser2/WritableStream";

const parserStream = new WritableStream({
    ontext(text) {
        console.log("Streaming:", text);
    },
});

const htmlStream = fs.createReadStream("./my-file.html");
htmlStream.pipe(parserStream).on("finish", () => console.log("done"));

Getting a DOM

The parseDocument helper parses a string and returns a DOM tree (a Document node).

import * as htmlparser2 from "htmlparser2";

const dom = htmlparser2.parseDocument(
    `<ul id="fruits">
        <li class="apple">Apple</li>
        <li class="orange">Orange</li>
    </ul>`,
);

parseDocument accepts an optional second argument with both parser and DOM handler options:

const dom = htmlparser2.parseDocument(data, {
    // Parser options
    xmlMode: true,

    // domhandler options
    withStartIndices: true, // Add `startIndex` to each node
    withEndIndices: true,   // Add `endIndex` to each node
});

Searching the DOM

The DomUtils module (re-exported on the main htmlparser2 export) provides helpers for finding nodes:

import * as htmlparser2 from "htmlparser2";

const dom = htmlparser2.parseDocument(`<div><p id="greeting">Hello</p></div>`);

// Find elements by ID, tag name, or class
const greeting = htmlparser2.DomUtils.getElementById("greeting", dom);
const paragraphs = htmlparser2.DomUtils.getElementsByTagName("p", dom);

// Find elements with custom test functions
const all = htmlparser2.DomUtils.findAll(
    (el) => el.attribs?.class === "active",
    dom,
);

// Get text content
htmlparser2.DomUtils.textContent(greeting); // "Hello"

For CSS selector queries, use css-select:

import { selectAll, selectOne } from "css-select";

const results = selectAll("ul#fruits > li", dom);
const first = selectOne("li.apple", dom);

Or, if you'd prefer a jQuery-like API, use cheerio.

Modifying and serializing the DOM

Use DomUtils to modify the tree, and dom-serializer (also available as DomUtils.getOuterHTML) to serialize it back to HTML:

import * as htmlparser2 from "htmlparser2";

const dom = htmlparser2.parseDocument(
    `<ul><li>Apple</li><li>Orange</li></ul>`,
);

// Remove the first <li>
const items = htmlparser2.DomUtils.getElementsByTagName("li", dom);
htmlparser2.DomUtils.removeElement(items[0]);

// Serialize back to HTML
const html = htmlparser2.DomUtils.getOuterHTML(dom);
// "<ul><li>Orange</li></ul>"

Other manipulation helpers include appendChild, prependChild, append, prepend, and replaceElement -- see the domutils docs for the full API.

Parsing feeds

htmlparser2 makes it easy to parse RSS, RDF and Atom feeds, by providing a parseFeed method:

const feed = htmlparser2.parseFeed(content);

This returns an object with type, title, link, description, updated, author, and items (an array of feed entries), or null if the document isn't a recognized feed format.

The xmlMode option is enabled by default for parseFeed. If you pass custom options, make sure to include xmlMode: true.

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 GitHub Actions (sourced from here):

htmlparser2        : 2.17215 ms/file ± 3.81587
node-html-parser   : 2.35983 ms/file ± 1.54487
html5parser        : 2.43468 ms/file ± 2.81501
neutron-html5parser: 2.61356 ms/file ± 1.70324
htmlparser2-dom    : 3.09034 ms/file ± 4.77033
html-dom-parser    : 3.56804 ms/file ± 5.15621
libxmljs           : 4.07490 ms/file ± 2.99869
htmljs-parser      : 6.15812 ms/file ± 7.52497
parse5             : 9.70406 ms/file ± 6.74872
htmlparser         : 15.0596 ms/file ± 89.0826
html-parser        : 28.6282 ms/file ± 22.6652
saxes              : 45.7921 ms/file ± 128.691
html5              : 120.844 ms/file ± 153.944

Security contact information

To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.