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

json-to-html-parser

v0.0.0

Published

Simpe json to html parser

Readme

Description

Each object from the JSON represents an HTML element. If the object contains a property called "elements" - array, the HTML element must adopt the elements nested in that array.

The types of HTML elements that the walker (processor, parser) supports are:

  • "container" (block element)
  • "label" (inline element)
  • "fieldset" (fieldset element)
  • "textfield" (input type text element)
  • "password" (input type password element)
  • "textarea" (textarea element)
  • "checkbox" (input type checkbox element)
  • "radio" (input type radio element)
  • "dropdown" (select element)
  • "submit" (input type submit element)

If an object contains a "label" property, the HTML form element must be printed together with a element, both wrapper inside a new "container" element, unless they are already nested inside a "container" - then we don't explicitly print new container. Field labels must be displayed on the left, unless the field is from the following types: "checkbox" or "radio" - then the label is shown on the right of the field. The value of the "label" property is used for text in the .

If an object has an "html" property, the value of that property must be set as inner HTML to the element. Then come the elements defined in "elements" property (if any).

Running

node parse index.json - creates a index.html file