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

wdio-facade

v1.0.6

Published

Facade/Wrapper utility library over WebdriverIO basic commands

Readme

wdio-facade

Facade/Wrapper utility library over WebdriverIO basic commands. This library is dependent on gtaa-interface-ts, which is a generic TypeScript interface with the purpose of providing an abstraction layer for automation JavaScript/TypeScript automation tools.

Abstraction Layer

Now, what do we mean by abstraction layer? According to ISTQB TAE as well as experience working with automation tools, they often get absolete in a couple of years or new better tools appear all the time on the market, and if we want to avoid having to rewrite all automation projects from scratch for each new framework that will appear in the future, better just build an abstraction layer over the tool that can be used by the business logic of TAS while designing automated test cases and decouple the device/browser interaction from the TAS Business Logic and allow the TAE to easily replace the tool being used with another at any moment in time, without too much impact on the previous hard work put into building the TAS. TAF_Design