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

xml-js-reader

v1.1.0

Published

Tool to read xml server responses and transform it into javascript.

Downloads

4

Readme

XML to Javascript

Tool to read xml server responses and transform it into javascript.

Example

const content = `<gu ok="one" nok="two">hello<ma ok="three" nok="four"></ma></gu>`
const js = toJs(content)
console.log(js)

Output

{
  "tag": "gu",
  "xmlTag": "<gu ok=\"one\" nok=\"two\">",
  "params": { "ok": "one", "nok": "two" },
  "children": [
    {
      "params": {},
      "tag": "",
      "xmlTag": "",
      "text": "hello",
      "children": [],
    },
    {
      "tag": "ma",
      "xmlTag": "<ma ok=\"three\" nok=\"four\">",
      "params": { "ok": "three", "nok": "four" },
      "children": [],
    },
  ],
}

Then you can reverse the process

console.(toXML(js))

Output

<gu ok="one" nok="two">hello<ma ok="three" nok="four"></ma></gu>

Object

Inline closed element

<ma ok="three" nok="four" />
    {
      "tag": "ma",
      "xmlTag": "<ma ok=\"three\" nok=\"four\" />",
      "params": { "ok": "three", "nok": "four" },
      "children": [],
    }

Parent element

<gu ok="one" nok="two">
  <ma ok="three" nok="four" />
</gu>
{
  "tag": "gu",
  "xmlTag": "<gu ok=\"one\" nok=\"two\">",
  "params": { "ok": "one", "nok": "two" },
  "children": [
    {
      "tag": "ma",
      "xmlTag": "<ma ok=\"three\" nok=\"four\" />",
      "params": { "ok": "three", "nok": "four" },
      "children": [],
    },
  ],
}

Text in element

<gu ok="one" nok="two">
  Hello
</gu>
{
  "tag": "gu",
  "xmlTag": "<gu ok=\"one\" nok=\"two\">",
  "params": { "ok": "one", "nok": "two" },
  "children": [
    {
      "params": {},
      "tag": "",
      "xmlTag": "",
      "text": "hello",
      "children": [],
    },
  ],
}

Prototype function

function callback(element) {
  return true
}

js.filter(callback)
js.findByTag('ma')
js.findByParam('ok', 'three')
js.findByPath(['a', 'b', 'c'])
  • filter Return all elements from the root where callback return true.
  • findByTag Return all elements from the root where tag equals.
  • findByParam Return all elements from the root where param is the first arguments and the value is the second.
  • findByPath Return all elements from the root where the path of tags to access is the ordered list of strings.

The filter function respect the order of occurences from top to bottom.

Bug report

You can contribute to this project, report issues and propose features.

  • Propose a feature that make sens by presenting a frequent usecase.
  • Report a bug with arguments, input and your expected output. Explain also you usecase.
  • Propose a pull request, start coding from the latest commit of master. Add unit tests and run all tests in the project.