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

oi-grease

v5.0.0

Published

Bunch of help methods for e2e automation testing via Puppeteer

Downloads

73

Readme

puppeteer-helpers

Bunch of help methods for e2e automation testing via Puppeteer

Purpose

Several examples why library exists:

  • You always have some troubles with click? waitForSelector() does not help sometimes and you use $eval(selector, (node) => node.click()? Please, stop clicking using JS if you write e2e UI tests. Our user does not interact with browser in such maner!

Was:

    await page.waitForSelector(selector, { timeout:30000 });
    await page.$eval(selector, (e: any) => e.click());

with Grease:

await click(page, selector);

click() will wait when Puppeteer find element and also when element become visible.

Library has other useful methods in API.md (TBD)

  • You aware Puppeteer does not have getText() method, strange but truth

Was:

 await page.waitForSelector(selector);
 const text = await page.$eval(selector, (el: any) => el.innerText);

with Grease:

const text = await getText(page, selector);

getText() will wait when Puppeteer find element and also when element become visible. Only after that get text of element.

API

TBD

Contribution guide

TBD