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

webdriverio-wait-and

v1.0.0

Published

Custom commands for WebdriverIO to wait for the element to be there, before doing an action on it.

Downloads

2

Readme

webdriverio-wait-and GitHub license npm

Custom commands for WebdriverIO to wait for the element to be there, before doing an action on it.

Usage

In your wdio.conf.js:

before () {
    require('webdriverio-wait-and');
},

In your tsconfig.json add webdriverio-wait-and to the types array.

In your tests:

$(".my-element").waitAnd().click();
$(".my-element").waitAndClick();
$(".my-element").waitAndSetValue("some value");

Also see

Be sure to also use expect-webdriver, which contains useful expectation helpers, that will wait for the condition to become true.

If you need to ensure that you are on a certain page you should use something like this:

expect(browser).toHaveUrlContaining("/my/page.html");

Why

Webtests are often flaky unless you wait for the elements to be there, before interacting with them. Because of this frameworks like Cypress do this by default.

In WebdriverIO the default solution for this is messy, and clutters up the code:

const element = $(".my-element");
element.waitForClickable();
element.click();