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

init-puppeteer

v4.3.6

Published

Abstraction over Puppeteer

Downloads

3

Readme

Init-puppeteer

It starts a Puppeteer instance and attaches multiple helpers to it. It includes also helpers to turn Puppeteer into a end-to-end testing framework.

Install

`yarn add https://github.com/selfrefactor/init-puppeteer#5.8.0``

Env

MATCH_DIR
HEADLESS_TEST
SCREEN_DIR

API

initPuppeteer(options: Options): Output

Such as options follow this Typescript rules:

  extraProps?: object
  resolution?: Resolution
  url?: string
  mobile?: boolean
  headless?: boolean
  waitCondition?: WaitConditions
  logFlag?: boolean

Snaps

pass PUPPETEER_SNAP as OFF to forbid _.snap to take screenshots

Step delay

Set process.env.STEP_DELAY=1000 for 1 second delay after each $ or $$ evaluation.

Debug

If process.env.PUPPETEER_DEBUG = 'true' then headless mode is turned off even if we pass headless:true during initialization.

Example

const { initPuppeteer } = require('init-puppeteer')

const ILEARNSMARTER = 'https://ilearnsmarter.com/'

void async function debug() {
  try {
    console.log('start')
    var { browser, page } = await initPuppeteer({
      headless: false,
      logFlag: false,
      url: ILEARNSMARTER,
    })

    const _ = attach(page)
    const x = await _.$$('div', els => els.length)
    console.log({x})

    await browser.close()
  } catch (e) {
    console.log(e)
  }
}()

Typescript example

import { initPuppeteer } from 'init-puppeteer'
import {
  InputPuppeteer,
  OutputPuppeteer,
} from 'init-puppeteer/typings'

async function fn(): Promise<void>{
  try{
      const settings: InputPuppeteer = {
        headless: true,
        url: 'about:blank',
      }

      var { browser, page }: OutputPuppeteer = await initPuppeteer(settings)
      // WORK
      return
     }catch (err){
    console.log(err)
  }finally{
    console.log('closing Chrome')
    if (browser !== undefined){
      await browser.close()
    }
  }
}

input.waitCondition

Could be a string among LOAD, NETWORK, DOM. In this case timeout is 60 seconds.

It can be also Puppeteer's NavigationOptions in which case input.waitCondition will passed directly to page.goto.