dom-parser

library1.1.5jsnpmunverified

dom-parser is a lightweight, zero-dependency library for parsing HTML and XML documents into a DOM-like structure using regular expressions. It provides a subset of standard DOM API methods like `getElementById`, `getElementsByClassName`, and `getElementsByTagName`, along with common node properties such as `innerHTML` and `textContent`. The current stable version is 1.1.5. Due to its regexp-based parsing, it is notably fast and compact, making it suitable for environments where full-fledged, specification-compliant DOM parsing (like `jsdom` or browser DOMParser) is overkill or too resource-intensive. Its main differentiator is performance and minimal footprint by leveraging regexps, though this approach might have limitations with highly malformed or complex HTML structures compared to state-machine parsers.

serialization web-framework data

npm install dom-parser

github ↗package ↗

INSTALL

IMPORT

SIG · DOM-PARSER

dom-parser

serializationjavascriptv1.1.5

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

parseFromString

✓ import { parseFromString } from 'dom-parser';

✗ const { parseFromString } = require('dom-parser');

The library primarily uses named exports. While CommonJS `require` might work in some transpiled environments, native ESM import is the intended and officially supported way for modern JavaScript and TypeScript projects.

Dom

✓ import type { Dom } from 'dom-parser';

When importing the type for the parsed DOM object (returned by `parseFromString`), use `import type` for clarity and to ensure it's stripped from the JavaScript output.

Node

✓ import type { Node } from 'dom-parser';

To reference the type for individual DOM nodes, `import type { Node } from 'dom-parser';` is the correct approach. This represents the generic node interface with properties like `nodeName`, `attributes`, and methods like `getAttribute`.

This example demonstrates parsing an HTML string, finding elements by ID, and then by class name within a specific element, and accessing attributes.

import { parseFromString } from 'dom-parser'; // Simulate reading an HTML file asynchronously async function simulateReadFile(filePath: string): Promise<string> { if (filePath === 'htmlToParse.html') { return ` <div id="rootNode"> <p class="childNodeClass">Hello from child 1</p> <span class="childNodeClass">Hello from child 2</span> <a href="#" name="mylink">Link</a> </div> <div class="childNodeClass">Another root child</div> `; } return ''; } async function main() { const html = await simulateReadFile('htmlToParse.html'); // Getting DOM model const dom = parseFromString(html); // Searching Nodes const rootNode = dom.getElementById('rootNode'); if (rootNode) { console.log('Found rootNode with id:', rootNode.nodeName); const childNodes = rootNode.getElementsByClassName('childNodeClass'); console.log('Children with class "childNodeClass":', childNodes.length); childNodes.forEach(node => console.log(' - Child text:', node.textContent)); const myLink = rootNode.getElementsByName('mylink')[0]; if (myLink) { console.log('Found link href:', myLink.getAttribute('href')); } } } main();

Debug

Known issues

gotchaDue to its RegExp-based parsing approach, `dom-parser` might not always produce a DOM structure identical to what a browser's native DOMParser or a compliant library like `jsdom` would for highly malformed or edge-case HTML. It prioritizes speed and simplicity over full HTML5 specification compliance.

fix

For mission-critical applications or when dealing with highly varied and potentially non-standard HTML, consider using a full HTML5 compliant parser (e.g., `jsdom` in Node.js or `DOMParser` in browsers) if strict parsing rules are required. Test thoroughly with your specific HTML inputs.

affects: >=1.0.0

gotchaThe `Node` API provided by `dom-parser` is a subset of the standard browser DOM API. While common methods like `getElementById`, `getElementsByClassName`, and properties like `innerHTML` are present, more advanced features or less common properties/methods of the native DOM (e.g., `querySelector`, event handling, style manipulation) are not implemented.

fix

Review the API documentation carefully for available methods and properties. If you require functionality not present in `dom-parser`, you may need to implement custom logic or opt for a more comprehensive DOM library.

affects: >=1.0.0

Errors

Common errors & fixes

TypeError: dom.getElementById is not a function

Attempting to call a DOM method on `dom` directly before parsing, or on an incorrect object.

fix

Ensure you have correctly called `parseFromString(htmlContent)` and are calling methods on the returned `Dom` object. Example: `const dom = parseFromString(html); const root = dom.getElementById('myId');`

Property 'textContent' does not exist on type 'Node'

TypeScript error indicating that the `Node` type might not explicitly declare `textContent` (though the library's `Node` interface *does* have it, this can happen if types are misaligned or if a different `Node` type is implicitly used).

fix

Verify that `dom-parser`'s types are correctly installed and configured. Ensure you are importing `Node` from `dom-parser` if you are explicitly typing your variables. If the issue persists, consider type assertion: `(myNode as any).textContent` or more specifically `(myNode as HtmlNode).textContent` if `HtmlNode` type is exported and applicable.

Upgrade

Version history

1.1.5latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

13 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/ershov-konst/dom-parser ↗

packagehttps://www.npmjs.com/package/dom-parser ↗