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

@acdrdev/shr

v1.0.0

Published

Hot reloading for scrapping with puppeteer

Readme

Scrap hot reloading

How to use?

Install package

  npm install @acdrdev/shr

Call the shrConfig function just below where you raise the browser instance and pass it as a parameter in the function, e.g.:

  import puppeteer from "puppeteer";
  import { shrConfig } from "@acdrdev/shr";

  const browser = await puppeteer.launch({
    headless: false
  })
  await shrConfig(browser)

Now just run the scrapper and use the following comments to re-run the parts of the scrapper you need:

| Comment | Actions | | ------- | ------------------------------ | | //--> | To execute the following line. | | //<-- | To execute the previous line. |

You can use both comments together to indicate code blocks, e.g.:

  import puppeteer from "puppeteer";
  import { shrConfig } from "@acdrdev/shr";

  const browser = await puppeteer.launch({
    headless: false
  })
  await shrConfig(browser)

  const pages = await browser.pages()
  const page = pages[0] || await browser.newPage()
  await page.goto('https://aratiendas.com/', {
    waitUntil: 'domcontentloaded'
  })

  //-->

  await page.select('div[data-id="976483c"] select', "centro-Bogota")
  const pageSource = await page.content()

  //<--

By default to work the browser instance variable is called “browser”, the page instance variable is called “page” and it will execute the code in the tab with index 0, but these values can be modified in the same comments as follows:

  //--> browserName: browserInstance, pageName: context, pageIndex: 1
  await context.select('div[data-id="976483c"] select', "centro-Bogota")
  const pageSource = await context.content()
  //<--

With the previous code we indicate that when we call the variable “browserInstance” we are referring to the browser instance, when we call the variable “context” we are referring to the instance of the page and that it will work in the tab with index 1 (the second tab), this properties can be indicated in any of the two comments and it does not matter their order, e.g.:

  //--> browserName: browserInstance, pageName: context, pageIndex: 1

or

  //<-- pageName: context, browserName: browserInstance, pageIndex: 1