saxes
npmv6.0.0TypeScriptAn evented streaming XML parser in JavaScript
Not recommended for new projects
No — saxes should not be adopted for new projects. Last published 1767 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1767 days ago.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 160 KB installed (at least — some of the tree is still being crawled).
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
ISC — 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 saxes 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.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Compatibility
- Node.js
- node >=v12.22.7
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the saxes README.
var saxes = require("./lib/saxes"),
parser = new saxes.SaxesParser();
parser.on("error", function (e) {
// an error happened.
});
parser.on("text", function (t) {
// got some text. t is the string of text.
});
parser.on("opentag", function (node) {
// opened a tag. node has "name" and "attributes"
});
parser.on("end", function () {
// parser stream is done, and ready to have more stuff written to it.Dependencies
Declared by saxes v6.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (32)
Used by
Popular packages that depend on saxes.
Relationship graph
Dependencies (left) and dependents (right) of saxes.
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.
A per-spec XML serializer implementation
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
Release history
No releases in the last two years, typically about 7 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 6.0.0latest | 4 years ago | 160 KB | ISC |
| 6.0.0-rc.1 | 4 years ago | 160 KB | ISC |
| 5.0.1 | 6 years ago | 160 KB | ISC |
| 5.0.0 | 6 years ago | 160 KB | ISC |
| 5.0.0-rc.2 | 6 years ago | 160 KB | ISC |
| 5.0.0-rc.1 | 6 years ago | 3.0 MB | ISC |
| 4.0.2 | 7 years ago | 103 KB | ISC |
| 4.0.1 | 7 years ago | 103 KB | ISC |
| 4.0.0 | 7 years ago | 103 KB | ISC |
| 4.0.0-rc.4 | 7 years ago | 102 KB | ISC |
| 4.0.0-rc.3 | 7 years ago | 102 KB | ISC |
| 4.0.0-rc.2 | 7 years ago | 101 KB | ISC |
| 4.0.0-rc.1 | 7 years ago | 100 KB | ISC |
| 3.1.11 | 7 years ago | 87 KB | ISC |
| 3.1.10 | 7 years ago | 81 KB | ISC |
Overview
saxes is an npm package that an evented streaming XML parser in JavaScript. It has 1 known dependents in the graph. The latest version is 6.0.0, released under the ISC license.
Who should use it
Teams working in the npm ecosystem who need an evented streaming XML parser in JavaScript and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (ISC).
Cons
- Large dependency tree (33 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use saxes?
No — saxes should not be adopted for new projects. Last published 1767 days ago.
How do I install saxes?
Run `npm install saxes` to add saxes to your npm project.
How many dependencies does saxes have?
saxes declares 33 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 160 KB on disk.
What license is saxes released under?
saxes is distributed under the ISC license.
How popular is saxes?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on saxes.
Is saxes still maintained?
The most recent release of saxes (v6.0.0) was published 4 years ago.
Does saxes run install scripts?
No. saxes does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.