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

@tdd-buffet/selenium

v0.4.28

Published

Selenium tools for tdd-buffet

Downloads

38

Readme

Selenium tools for tdd-buffet

Build Status codecov


Requirements

  • Docker 1.12.0+
  • docker-compose 1.18.0+

Install

npm install @tdd-buffet/selenium

Start a grid with Chrome and Firefox

npx @tdd-buffet/selenium start [N=1] --port 4444 --retries 15

The hub will listen at 0.0.0.0:4444 and it will have 2*N browser nodes (N Chrome and N Firefox):

Start a grid with debug nodes with VNC

npx @tdd-buffet/selenium debug --port 3333 --retries 15

The same hub as above will spin up, but this time only 2 nodes (Chrome and Firefox) with VNC enabled will connect. VNC is available at 0.0.0.0:5900 (Chrome) and 0.0.0.0:5901 (Firefox).

Connect other containers

When spinning up the grid a network named tdd-buffet is created. You can make other containers visible to the grid nodes by having them join the same network - they will then be accessible through their name. Here's an example using docker-compose:

version: '2.1'

services:
  my-service:
    image: nginxdemos/hello
    networks:
      - tdd-buffet
    expose:
      - 80

networks:
  tdd-buffet:
    external: true # this tells docker-compose that the
                   # network was created outside this project
npx @tdd-buffet/selenium start
docker-compose up -d
# Now you can tell the hub to access http://my-service

network

Stop everything

npx @tdd-buffet/selenium stop