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 🙏

© 2024 – Pkg Stats / Ryan Hefner

get-xml

v1.0.0

Published

Parse XML in Node and the browser seamlessly

Downloads

70

Readme

get-xml

This is a very simple module. Use it whenever you need to parse XML into a DOM, in either Node or the browser, transparently.

When running in Node, this will use xmldom to process the XML. When loaded in a browser there is no such dependency and the browser's native XML processing will be used. This can lead to differences in DOM behaviour, but so long as you stick to tried-and-true DOM usage you will be fine.

NOTE: This only works with bundlers that respect the browser field in package.json (Browserify does, I guess the other big ones do too).

Installation

npm install get-xml

API

import { parseString } from 'get-xml';
let doc = parseString(someXML);

Or for those of you who like your JS retro:

var parseString = require('get-dom').parseString;
var doc = parseString(someXML);

You can look under example-browser to see how this works in the browser, once browserified.