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

digger-xml

v0.2.3

Published

The XML parser for digger container data

Downloads

12

Readme

digger-xml

Build status

An XML parser/stringifier for digger container data

example

var XML = require('digger-xml');
var data = XML.parse('<folder name="hello"><thing name="thing" /></folder>');
var xml_string = XML.stringify(data);

data becomes:

[{
	name:'hello',
	_digger:{
		tag:'folder'
	},
	_children:[{
		name:'thing',
		_digger:{
			tag:'thing'
		}
	}]
}]

xml_string becomes:

<folder name="hello"><thing name="thing" /></folder>

installation

as a node module:

$ npm install digger-xml

or in the browser using browserify

usage

Both versions work the same in the browser or on the server.

The server version uses xmldom for the XML parsing.

The browser version uses the native browser parsers.

parse

Takes a string and returns digger data

var data = XML.parse('<folder name="hello"><thing name="thing" /></folder>');

If there is an 'attr' element as a direct child - it is applied as an attribute of the parent:

<blog title="my post">
<attr name="content">hello world</attr>
</blog>

This is turned into:

[{
	content:'hello world',
	_digger:{
		tag:'blog'
	}
}]

stringify

Takes an array of digger data and returns an XML string.

Attributes are turned into nodes if they are strings and more than 32 chars long or container a \n char.

var XML = require('digger-xml');
var data = [{
	content:"hello \nworld",
	_digger:{
		tag:'blog'
	}
}]

var xml_string = XML.stringify(data);

This outputs:

<blog title="my post">
<attr name="content">hello 
world</attr>
</blog>

tests

There are 2 sets of tests one for the npm node version and one for the component.

To run the server tests:

$ make test

And the browser ones (using phantomjs which you need to install):

$ make browser-test

licence

MIT