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

@watershed-labs/driver-factory

v0.1.0

Published

Browser and device session factory for the Watershed ecosystem

Readme

@watershed-labs/driver-factory

Browser and device session factory for the Watershed ecosystem.

Part of the Watershed testing ecosystem.


Overview

@watershed-labs/driver-factory handles browser and device session creation for every Watershed template that interacts with a browser. It abstracts Chrome, Firefox, Edge, Safari, and Brave initialisation — including WebDriver BiDi capability enabling, post-launch Brave detection, and correct session teardown.

Keeping session creation here means BiDi upgrades, Brave patches, and new browser support land in one place and propagate to all affected templates automatically.


Installation

npm install @watershed-labs/driver-factory

Usage

import { BrowserFactory } from '@watershed-labs/driver-factory';
import { config } from '@watershed-labs/config';

const driver = await BrowserFactory.create({
    browser:  config.get('browser'),   // chrome | firefox | edge | safari
    headless: config.get('headless'),
    bidi:     true,                    // WebDriver BiDi enabled by default
});

await driver.detectBrave();            // post-launch Brave probe

API

| Method | Description | |---|---| | BrowserFactory.create(options) | Creates a new WebDriver session with BiDi enabled by default. Returns an augmented Driver instance. | | driver.detectBrave() | Post-launch Brave detection via navigator.brave JS probe. Caches result on instance. Call once after session creation. | | driver.initBiDi() | Upgrades the session to a BiDi WebSocket connection. Called automatically if bidi: true. | | driver.isBrave | Boolean. Available after detectBrave() is called. Use to gate Brave-specific behaviour. | | driver.quit() | Cleanly terminates the WebDriver session and closes the BiDi WebSocket connection. |


Options

| Option | Type | Default | Description | |---|---|---|---| | browser | string | 'chrome' | Browser target: chrome, firefox, edge, safari | | headless | boolean | true | Run in headless mode | | bidi | boolean | true | Enable WebDriver BiDi via webSocketUrl capability | | debugPort | number | auto | CDP debug port. Auto-derived from CUCUMBER_WORKER_ID in parallel runs. | | browserVersion | string | 'stable' | Browser channel. Always use 'stable' in CI. |


Brave Detection

Brave reports itself to WebDriver as Chrome. Detection must be done post-launch via a JavaScript probe. Do not check browserName === 'brave' — it will never be true.

await driver.detectBrave();

if (driver.isBrave) {
    // Skip canvas-dependent assertions
    // CDP device emulation results may not be pixel-perfect
}

Parallel Safety

Safe. Each worker owns an independent session. The factory automatically derives a unique CDP debug port from CUCUMBER_WORKER_ID using 9222 + parseInt(workerId) to prevent port collisions. Never pass a fixed --remote-debugging-port argument when running in parallel.


Licence

MIT — part of the Watershed ecosystem.