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-brillo

v1.1.2

Published

Puppeteer tools to help you scrape websites

Downloads

2

Readme

puppeteer-brillo

Puppeteer tools to help you scrape websites

Functions

  • getText(el: ElementHandle): Promise<string> read the innerText from an element handle.
  • saveScreenshotAndHtml(page: Page, label: string): Promise<void> Only enabled when process.env.DEBUG is set. Captures a screenshot of the current page and the html structure, saving them to files.
  • waitForText(page: Page, value: string | string[], opts: { timeout: number }): Promise<string> Wait up to timeout ms for value to appear as text in the page. If value is an array, wait for any of it's entries to appear. Returns the value found, or throws a TimeoutError.
  • findAllWithText(page: Page, selector: string: value: string | RegExp, opts: { timeout?: number, exact?: boolean, scope?: ElementHandle } = {}) find all elements within page matching selector that contain value as text. If exact is true, the element must contain exactly that text. If scope is passed, only consider elements within that DOM subtree. If timeout is passed, wait for up to that long (ms) to see if such an element appears.
  • findOneWithText(...) just like findAllWithText, but errors if no match is found, and warns if more than one is found.
  • furthestAncestorWithout(child: ElementHandle, childToAvoid: ElementHandle): Promise<ElementHandle | null> Return the earliest ancestor of child that does not contain the avoid element.
  • nearestParentLike(child: ElementHandle, selector: string): Promise<ElementHandle | null> find the closest ancestor to child that matches selector.
  • commonAncestor(a: ElementHandle, b: ElementHandle): Promise<ElementHandle | null> find the closest element that contains both a and b.
  • waitForNetworkIdle(page: Page, idleMs: number, opts: NetworkIdleOptions): Promise<void> Attach network listeners to watch for outstanding requests. Resolve once all are settled. Set opts.maxInflightRequests to a positive number to allow resolving while there are still requests outstanding. Set opts.skipRequest to determine that some requests are not worth waiting for.
  • whileWaitingForNetworkIdle<T>(page: Page, idleMs: number, opts: NetworkIdleOptions, action: () => Promise<T>): Promise<T> Attach network listeners to watch for outstanding requests, call action, and then resolve once all outstanding requests have returned. Useful to ensure that data fetched in response to a button click has all arrived on the page.