Package Health Score

82 / 100

security
No known security issues
popularity
Influential project
maintenance
Sustainable
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
1.4.1	\|	04/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.0	\|	04/2022	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.2	\|	11/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.1	\|	02/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.0.1	\|	06/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (36,554,008)

GitHub Stars: 121
Forks: 70
Contributors: 30

Direct Usage Popularity

The npm package dom-serializer receives a total of 36,554,008 downloads a week. As such, we scored dom-serializer popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package dom-serializer, we found that it has been starred 121 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 30
Funding: Yes

With more than 10 contributors for the dom-serializer repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like dom-serializer is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 2
Open PR: 3
Last Release: 3 years ago
Last Commit: 17 days ago

Further analysis of the maintenance status of dom-serializer based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

An important project maintenance signal to consider for dom-serializer is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 11 years
Dependencies: 3 Direct
Versions: 18
Install Size: 28.8 kB
Dist-tags: 1
# of Files: 16
Maintainers: 1
TS Typings: Yes

dom-serializer has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use dom-serializer?

To help you get started, we've collected the most common ways that dom-serializer is being used within popular public projects.

wxajs / wxa / packages / wxa-cli / src / tester / domWalker.js View on Github

let [, $1] = /bind(?::)?([\w]*)/g.exec(attr);
                if (!!~this.supportEvents.indexOf($1)) {
                    eventMap += `|${$1}:${attributes[attr]}`;
                    element.attribs[`bind${$1}`] = `$$e2e_${$1}`;
                }
            });

            eventMap = eventMap.replace(/^\|/, '');
            element.attribs['data-_wxaTestEventMap'] = eventMap;

            // generate unique id for tag.
            // pagePath + hash(parentNode + prevNode) + optional(class/id)
            let pagePath = path.relative(this.scheduler.wxaConfigs.context, path.dirname(this.mdl.src) + path.sep + path.basename(this.mdl.src, path.extname(this.mdl.src)));

            let ele = this.getParentAndPrevNode(element);
            let eleString = new Coder().decodeTemplate(domSerializer(ele, {xmlMode: true}));
            let hash= getHashWithString(eleString);

            let {isIeration, indexVariable} = this.findSelfOrAncestorIterationDirective(element);

            let keyElement = [pagePath, hash, element.attribs.id];
            if (isIeration) keyElement.push(`-{{${indexVariable}}}`);

            let id = this.assembleUniqueId(keyElement);
            element.attribs['data-_wxaTestUniqueId'] = id;
            element.attribs['class'] = this.dropSpace((element.attribs['class'] || '') + ' '+ id);
        }
    }

View more ways to use dom-serializer

dom-serializer

Renders a domhandler DOM node or an array of domhandler DOM nodes to a string.

import render from "dom-serializer";

// OR

const render = require("dom-serializer").default;

API

`render`

▸ render(node: Node | Node[], options?: Options): string

Renders a DOM node or an array of DOM nodes to a string.

Can be thought of as the equivalent of the outerHTML of the passed node(s).

Parameters:

Name	Type	Default value	Description
`node`	Node \| Node[]	-	Node to be rendered.
`options`	DomSerializerOptions	{}	Changes serialization behavior

Returns: string

Options

`encodeEntities`

• Optional decodeEntities: boolean | "utf8"

Encode characters that are either reserved in HTML or XML.

If xmlMode is true or the value not 'utf8', characters outside of the utf8 range will be encoded as well.

default decodeEntities

`decodeEntities`

• Optional decodeEntities: boolean

Option inherited from parsing; will be used as the default value for encodeEntities.

default true

`emptyAttrs`

• Optional emptyAttrs: boolean

Print an empty attribute's value.

default xmlMode

example With emptyAttrs: false: <input checked>

example With emptyAttrs: true: <input checked="">

`selfClosingTags`

• Optional selfClosingTags: boolean

Print self-closing tags for tags without contents.

default xmlMode

example With selfClosingTags: false: <foo></foo>

example With selfClosingTags: true: <foo />

`xmlMode`

• Optional xmlMode: boolean | "foreign"

Treat the input as an XML document; enables the emptyAttrs and selfClosingTags options.

If the value is "foreign", it will try to correct mixed-case attribute names.

default false

Ecosystem

Name	Description
htmlparser2	Fast & forgiving HTML/XML parser
domhandler	Handler for htmlparser2 that turns documents into a DOM
domutils	Utilities for working with domhandler's DOM
css-select	CSS selector engine, compatible with domhandler's DOM
cheerio	The jQuery API for domhandler's DOM
dom-serializer	Serializer for domhandler's DOM

LICENSE: MIT

dom-serializer dependencies

domelementtype domhandler entities

dom-serializer development dependencies

@types/jest @types/node @typescript-eslint/eslint-plugin @typescript-eslint/parser cheerio eslint eslint-config-prettier htmlparser2 jest prettier ts-jest typescript

FAQs

What is dom-serializer?

render domhandler DOM nodes to a string. Visit Snyk Advisor to see a full health score report for dom-serializer, including popularity, security, maintenance & community analysis.

Is dom-serializer popular?

The npm package dom-serializer receives a total of 36,554,008 weekly downloads. As such, dom-serializer popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is dom-serializer well maintained?

We found indications that dom-serializer maintenance is sustainable demonstrating some project activity. We saw a total of 30 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is dom-serializer safe to use?

The npm package dom-serializer was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 22 November-2024, at 05:03 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP