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

@cpclermont/hq

v1.0.3

Published

jq's not sophisticated HTML cousin

Readme

hq

jq's not as sophisticated cousin but for HTML.

Installation

# with npm
npm install -g @cpclermont/hq

# with yarn
yarn global add @cpclermont/hq

Usage

HTML isn't as well structured as JSON. But we can do some fun stuff with CSS selectors and attribute selectors.

hq commands all start with a CSS selector and are then optionally passed into a transformation:

# example settings
url="https://www.webpagetest.org"
cssSelector="head > script[src]:not([defer]):not([async])"

# examples
curl -s $url | hq "$cssSelector"
curl -s $url | hq "$cssSelector | html"
curl -s $url | hq "$cssSelector | text"
curl -s $url | hq "$cssSelector | innerHTML"
curl -s $url | hq "$cssSelector | attr(src)"
curl -s $url | hq "$cssSelector | attr(src, href)"

Transformations

  • html (alias: outerHTML) returns the outerHTML of the node.

  • text returns the text in the node.

  • innerHTML returns the innerHTML of the node :grimacing:.

  • attr(attrs) returns the values of the attributes(comma separated). The output of unmatched attributes is skipped, every attribute is output to a new line.

    This exists so you can scrape URLs from different node types that might live in different attributes.

    e.g.

    curl -s https://www.webpagetest.org | hq '
      head > script[src]:not([defer]):not([async]),
      head > link[rel=stylesheet]
      | attr(src, href)'

    Where we want to list render blocking scripts and stylesheets in the order they are found.

Examples

# Get URLs of scripts that are render blocking
curl -s https://www.webpagetest.org | hq '
  head > script[src]:not([defer]):not([async])
  | attr(src)'

# Get URLs of scripts and stylesheets that are render blocking
curl -s https://www.webpagetest.org | hq '
  head > script[src]:not([defer]):not([async]),
  head > link[rel=stylesheet]
  | attr(src, href)'

Notes

This is scrappy and nowhere near as good as jq. But it's better than nothing :)

License

MIT