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

@lancejpollard/resilient-puppeteer.js

v0.2.4

Published

By default, on normal real-world web-pages, the Puppeteer library for Node.js will crash for a variety of difficult to describe situations. This just makes it so you can know that your web page rendering script will _eventually_ be successful, recovering

Downloads

6

Readme

Resilient Puppeteer

By default, on normal real-world web-pages, the Puppeteer library for Node.js will crash for a variety of difficult to describe situations. This just makes it so you can know that your web page rendering script will eventually be successful, recovering from errors and making sure it continues to chug along processing more pages.

Also, we make it easy to add proxy support, as it's sometimes important to add a proxy.

npm install @lancejpollard/resilient-puppeteer.js
const resilient = require('@lancejpollard/resilient-puppeteer.js')

start()

async function start() {
  await resilient.launch()

  const urls = [...]

  for (let i = 0, n = urls.length; i < n; i++) {
    const url = urls[i]
    // it's not going to crash.
    await resilient.visit(url)
    // it can crash here if your DOM code is incorrect though,
    // but that is what you want.
    const hrefs = await resilient.evaluate(getLinks)
    // insert them to db or something otherwise.
    console.log(hrefs)
    // sometimes it helps to just wait :)
    await resilient.wait(1000)
  }

  await resilient.close()

  function getLinks() {
    const links = {}
    Array.prototype.slice.call(document.querySelectorAll('a')).forEach(a => {
      links[a.href] = true
    })
    return Object.keys(links)
  }
}

Can go into headed mode if you want as well.

await resilient.launch({ headless: false })

You can use a proxy as well:

const proxy = `https://zproxy.lum-superproxy.io:22225`
const username = `lum-customer-m1_3918c719-zone-zone1`
const password = `cjia091jioa`

await resilient.launch({
  proxy,
  username,
  password
})