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 🙏

© 2025 – Pkg Stats / Ryan Hefner

micro-parse

v1.0.4

Published

Easily parse & consume [microdata](https://developer.mozilla.org/en-US/docs/Web/HTML/Microdata)

Downloads

13

Readme

micro-parser

Easily parse & consume microdata

Installation

npm i micro-parse

Basic Usage

import microdataParse from "micro-parse";
const html = '<div itemscope itemtype="https://schema.org/SoftwareApplication">...</div>'
console.log(microdataParse(html));

Response Structure

The above should produce an object with the following structure, mapping identically to the microdata hierarchy of its source data:

{ scope: 'https://schema.org/SoftwareApplication', metadata: {...}, children: [...] }

In the above, scope indicates a defined microdata scope, metadata represents all data associated with the given scope level, and children includes all sub-scopes (array members are objects repeating the above structure)

Client-side Execution

In unusual cases where metadata is updated client-side, we can allow script execution as follows:

const html = '<div itemscope itemtype="https://schema.org/SoftwareApplication">...</div>'
const options = { runScripts: "dangerously" };
console.log(microdataParse(html, options));

Note that you incur some risk when running unknown scripts. Warning from JSDOM docs:

...this is also highly dangerous when dealing with untrusted content. The jsdom sandbox is not foolproof, and code running inside the DOM's s can, if it tries hard enough, get access to the Node.js environment, and thus to your machine.

Additional Options

All options passed will be relayed to JSDOM – as such, all JSDOM-supported options are available. Absence of the options argument will instead leverage node-html-parser, often yielding performance gains north of 50%.