w3c-xmlserializer
npmv5.0.0A per-spec XML serializer implementation
Adopt with care
w3c-xmlserializer is usable, with caveats. Last published 1033 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- DMaintenance: grade D, Poor — a real concern.
Last published 1033 days ago.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 31 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 6 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding w3c-xmlserializer to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing w3c-xmlserializer, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=18
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the w3c-xmlserializer README.
const { JSDOM } = require("jsdom");
const { document } = new JSDOM().window;
const node = document.createElement("akomaNtoso");w3c-xmlserializer vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| w3c-xmlserializerthis page | 0 | 1 | MIT | 2 years ago |
| cheerio | 24.1M | 5 | MIT | 1 day ago |
| happy-dom | 0 | 6 | MIT | 1 day ago |
| jsdom | 0 | 20 | MIT | 1 day ago |
| dom-serializer | 94.3M | 2 | MIT | 1 day ago |
| @testing-library/jest-dom | 56M | 6 | MIT | 1 day ago |
Dependencies
Declared by w3c-xmlserializer v5.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (3)
Used by
Popular packages that depend on w3c-xmlserializer.
Relationship graph
Dependencies (left) and dependents (right) of w3c-xmlserializer.
Frequently installed together
An implementation of the WHATWG URL Standard's URL API and parsing machinery
An HTTP/1.1 client, written from scratch for Node.js
An AST-based pattern checker for JavaScript.
Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
An arbitrary-precision Decimal type for JavaScript.
Implements the WebIDL algorithms for converting to and from JavaScript values
Parses, serializes, and manipulates MIME types, according to the WHATWG MIME Sniffing Standard
CSS color - Resolve and convert CSS colors.
Validates whether a string matches the production for an XML name or qualified name
CSS syntax patches for CSS tree
A tool set for CSS: fast detailed parser (CSS → AST), walker (AST traversal), generator (AST → CSS) and lexer (validation and matching) based on specs and browser implementations
Sniff the encoding from a HTML byte stream
Release history
No releases in the last two years, typically about 64 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 5.0.0latest | 2 years ago | 18 KB | MIT |
| 4.0.0 | 3 years ago | 18 KB | MIT |
| 3.0.0 | 5 years ago | 18 KB | MIT |
| 2.0.0 | 6 years ago | 18 KB | MIT |
| 1.1.2 | 7 years ago | 22 KB | MIT |
| 1.1.1 | 7 years ago | 22 KB | MIT |
| 1.1.0 | 7 years ago | 22 KB | MIT |
| 1.0.1 | 7 years ago | 21 KB | MIT |
| 1.0.0 | 8 years ago | 21 KB | MIT |
| 0.0.4-0 | 8 years ago | 21 KB | MIT |
| 0.0.3 | 8 years ago | 21 KB | MIT |
| 0.0.2 | 8 years ago | 20 KB | MIT |
| 0.0.1 | 8 years ago | 20 KB | MIT |
Overview
w3c-xmlserializer is an npm package that a per-spec XML serializer implementation. It has 1 known dependents in the graph. The latest version is 5.0.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a per-spec XML serializer implementation and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Keywords
Frequently asked questions
Should I use w3c-xmlserializer?
w3c-xmlserializer is usable, with caveats. Last published 1033 days ago.
How do I install w3c-xmlserializer?
Run `npm install w3c-xmlserializer` to add w3c-xmlserializer to your npm project.
How many dependencies does w3c-xmlserializer have?
w3c-xmlserializer declares 4 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 31 KB on disk.
What license is w3c-xmlserializer released under?
w3c-xmlserializer is distributed under the MIT license.
How popular is w3c-xmlserializer?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on w3c-xmlserializer.
Is w3c-xmlserializer still maintained?
The most recent release of w3c-xmlserializer (v5.0.0) was published 2 years ago.
Does w3c-xmlserializer run install scripts?
No. w3c-xmlserializer does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.