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

xml-explorer

v0.3.2

Published

React XML explorer with Monaco editor, XPath mapping and worker-based tree sync.

Readme

xml-explorer

React XML explorer component with:

  • Monaco XML editor
  • worker-based XPath indexing and cursor lookup
  • EN16931 BT/BG tree synchronization
  • strict vs nearest mapping mode

Usage

import { XMLExplorer } from "xml-explorer";
import type { TreeNode, XmlNamespaces } from "xml-explorer";

export function Example() {
  const tree: TreeNode = loadYourTreeDefinition();
  const namespaces: XmlNamespaces = loadYourNamespaces();
  return (
    <XMLExplorer
      xml={xmlString}
      syntax="xrechnung-cii"
      tree={tree}
      namespaces={namespaces}
    />
  );
}

xml-explorer does not ship a built-in BT/BG catalog or namespace map. Consumers must provide tree and namespaces. For example Tree and Namespace, see here The syntax prop is a user-defined key (string) used to select node.xpaths[syntax] across your tree.

Local development

npm install
npm run dev

The Vite app in this repo is a demo host for the package.

Install (consumer app)

npm install xml-explorer

Required peer dependencies in the consumer app:

  • react
  • react-dom
  • @monaco-editor/react
  • monaco-editor

Package API

  • XMLExplorer (named export)
  • buildRuntimeTree
  • buildMappingsForSyntax
  • types: XmlSyntax, XmlNamespaces, TreeNode, RuntimeTreeNode, NodeMapping, MatchLocation

Build package

npm run build

Outputs are written to dist/:

  • dist/index.js (ESM)
  • dist/index.cjs (CJS)
  • dist/index.d.ts (types)

Dry-run before publish

npm pack

Inspect the generated .tgz to confirm package contents.

Publish to npm

  1. Ensure package name/version in package.json are correct.
  2. Login once: npm login
  3. Publish: npm publish --access public

If the package name is already taken, use a scoped name like @your-scope/xml-explorer.