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

puppeteer-find

v0.1.0

Published

Find for Puppeteer ================== Simple yet powerful DOM querying API

Downloads

8

Readme

Find for Puppeteer

Simple yet powerful DOM querying API

Overview

All functionality is exposed in one function: find([ElementHandle $root], Array<Query> queries, [boolean returnId]).
Let's take a closer look at those parameters.

  • $root: an optional ElementHandle that serves as the root of the search. When left out, the document will be used.
  • returnId: because Puppeteer doesn't support returning HTML elements (yet?), we just assign an ID to the resulting element (if it doesn't already have one) and return that. When returnId is set to true, find() will just return that ID. When false, it will do an extra query and return the ElementHandle corresponding to the resulting element.
  • queries: this is the heart of the module, the place where all magic happens. queries is an array of Query objects, which consist of a selector and a where clause, containing some conditions.