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

madlib-xml-objectifier

v0.1.10

Published

Turns an XML DOM level 2 document into a JavaScript object

Downloads

41

Readme

madlib-xml-objectifier

Build Status NPM version Built with Grunt

Npm Downloads

A converter utility to turn an XML Document (DOM level 2) into a JavaScript object.

acknowledgments

The Marviq Application Development library (aka madlib) was developed by me when I was working at Marviq. They were cool enough to let me publish it using my personal github account instead of the company account. We decided to open source it for our mutual benefit and to ensure future updates should I decide to leave the company.

philosophy

JavaScript is the language of the web. Wouldn't it be nice if we could stop having to rewrite (most) of our code for all those web connected platforms running on JavaScript? That is what madLib hopes to achieve. The focus of madLib is to have the same old boring stuff ready made for multiple platforms. Write your core application logic once using modules and never worry about the basics stuff again. Basics including XHR, XML, JSON, host mappings, settings, storage, etcetera. The idea is to use the tried and proven frameworks where available and use madlib based modules as the missing link.

Currently madLib is focused on supporting the following platforms:

  • Web browsers (IE6+, Chrome, Firefox, Opera)
  • Appcelerator/Titanium
  • PhoneGap
  • NodeJS

installation

npm install madlib-xml-objectifier

usage

The xml-objectifier module exposes two main methods: documentToObject and nodeToObject. Both perform the same task and the only real reason for the documentToObject method to exist is as a convenience to get the root element automatically. This module is pure JavaScript (well CoffeeScript actually) and can be used directly in both browser and nodejs environments.

You might want to look at the following other madlib modules to use together with the objectifier:

documentToObject

var xmldom      = require( "madlib-xmldom"      );
var objectifier = require( "madlib-objectifier" );

var xmlDoc    = xmldom.parse( "<example><books><book>An example book</book></books></example>" );
var xmlObject = objectifier.documentToObject( xmlDoc, "smart" );

conversion modes

The objectifier can work in 3 modes: strict:

  • every tag is an array
  • attributes are separate
  • namespace support for tags and attributes
  • reversible with xml-deobjectifier

smart:

  • tags are arrays based on plural tag name detection
  • smart hinting can be used to force arrays
  • attributes are separate
  • no namespace support
  • mostly reversible with xml-deobjectifier

minimal:

  • flattens attributes and tags as much as possible
  • no namespace support
  • lossy conversion, not reversible

With the following example XML output would look like this:

<example>
    <books foo="bar">
        <book>An example book</book>
    </books>
</example>
strict:
{
    "example": {
        "$t": "",
        "books": [
            {
                "$t": "",
                "$a": {
                    "foo": {
                        "$t": "bar"
                    }
                },
                "book": [
                    {
                        "$t": "An example book"
                    }
                ]
            }
        ]
    }
}
smart:
{
    "example": {
        "books": {
            "$a": {
                "foo": {
                    "$t": "bar"
                }
            },
            "book": [
                "An example book"
            ]
        }
    }
}
minimal:
{
    "example": {
        "books": {
            "foo": "bar",
            "book": "An example book"
        }
    }
}

Beware that when you are using minimal mode and you have a tag with both text and attributes you will see the $t again:

<example>
    <books>
        <book isbn="12345">An example book</book>
    </books>
</example>
{
    "example": {
        "books": {
            "book": {
                "$t": "An example book",
                "isbn": "12345"
            }
        }
    }
}