npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

xml2js-fxp

v1.0.0

Published

xml2js-compatible parsing API backed by @nodable/flexible-xml-parser

Readme

xml2js-fxp

xml2js-compatible XML-to-JS parsing API, backed by @nodable/flexible-xml-parser.

Purpose: Users of xml2js can use new features without massive API migration overhead

import xml2js from 'xml2js-fxp';

const result = await xml2js.parseStringPromise('<root><item id="1">hello</item></root>');
// { root: { item: { $: { id: '1' }, _: 'hello' } } }

API

import { Parser, parseString, parseStringPromise, processors, defaults } from 'xml2js-fxp';

const parser = new Parser({ explicitArray: false });
const result = await parser.parseStringPromise(xml);

parseString(xml, (err, result) => { /* ... */ });
parseString(xml, { trim: true }, (err, result) => { /* ... */ });

Supported options

| Option | Default | Status | |---|---|---| | attrkey | '$' | ✅ | | charkey | '_' | ✅ | | explicitCharkey | false | ✅ | | trim | false | ✅ | | normalize | false | ✅ (custom whitespace-collapse parser) | | normalizeTags | false | ✅ | | explicitRoot | true | ✅ | | explicitArray | true | ✅ (root element is never array-wrapped) | | emptyTag | '' | ✅ (string or factory function) | | ignoreAttrs | false | ✅ | | mergeAttrs | false | ✅ | | validator | null | ✅ (post-parse hook, errors reject the promise / pass to callback) | | xmlns | false | ✅ (adds $ns: {local, uri} per element) | | explicitChildren | false | ✅ | | childkey | '$$' | ✅ | | preserveChildrenOrder | false | ✅ (adds #name to each $$ entry) | | charsAsChildren | false | ✅ | | includeWhiteChars | false | ✅ | | async | false | ✅ | | strict | true | ⚠️ approximate — maps to autoClose: null / 'html' | | attrNameProcessors | null | ✅ | | attrValueProcessors | null | ✅ | | tagNameProcessors | null | ✅ | | valueProcessors | null | ✅ |

xml2js.processors re-exports normalize, firstCharLowerCase, stripPrefix, parseNumbers, parseBooleans.

xml2js.defaults['0.1'] and ['0.2'] are provided for parity with xml2js.defaults, but must be applied manually (spread into your options) — they are not auto-selected.

Limitations

  • strict maps to autoClose: null (strict, default) or autoClose: 'html' (lenient). This is an approximation of sax-js's strict mode and may not produce identical recovery behavior for all malformed documents.
  • xml2js.Builder (JS object → XML serialization) is not implemented. This package covers parsing only. Consider xmlbuilder2 for the reverse direction.
  • Namespace support (xmlns: true) covers element namespace resolution ($ns: {local, uri}) for elements with prefixed/default namespaces. Namespace-prefixed attributes are not specially resolved beyond their literal name.

License

MIT