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

conductor-e2e

v0.1.2

Published

Multi-platform E2E test framework — web (Playwright), API, mobile (Maestro), desktop (JavaFX), and database in one Cucumber scenario

Readme

Conductor

CI npm version npm version License: MIT

A multi-platform E2E test framework where one Cucumber scenario can drive a web browser, a REST API, a Flutter mobile app, a JavaFX desktop app, and a database — all from TypeScript.

@cross-platform
Scenario: Todo created on web appears on the Flutter mobile app
  Given I am on the todo web application
  When I log in as "[email protected]" with password "secret"
  And I create a todo titled "E2E Cross Platform"
  Then the todo "E2E Cross Platform" appears on the web dashboard
  And the API should return the todo "E2E Cross Platform" with status "open"
  And the Flutter app should display "E2E Cross Platform" in the todo list

Stack

| Concern | Technology | |---|---| | BDD runner | @cucumber/cucumber v11 | | Web automation | Playwright | | API testing | Playwright APIRequestContext | | Mobile automation | Maestro CLI (Flutter / native) | | Desktop automation | javafx-driver (JavaFX) | | Database | Plugin interface (bring your own adapter) | | Reporting | Allure (allure-cucumberjs) |

Quick Start

npm install conductor-e2e

See the User Guide for a step-by-step walkthrough of bootstrapping a new E2E project from scratch.

Why Conductor?

Most E2E frameworks pick one platform. When your product lives on multiple platforms — a web dashboard, a mobile app, a REST API, a desktop client — you end up with N parallel test suites that can't share scenarios, page objects, or data lifecycle.

Conductor unifies them behind a single ConductorWorld:

async function (this: ConductorWorld) {
  await this.web.launch();                        // Playwright browser
  await this.page.goto('/login');                 // active page
  await this.api.post('/todos', { title: ... });  // shared HTTP client
  await this.maestro.runOrThrow('verify-todo');   // Flutter mobile flow
  await this.fx.locator('#save-btn').click();     // JavaFX desktop
  await this.db.query('SELECT ...');              // your adapter
}

Drivers are lazily instantiated. Tag-driven hooks manage their lifecycle:

| Tag | Effect | |---|---| | @web / @cross-platform | Launches browser, screenshots failures, closes | | @mobile / @cross-platform | Targets the configured Maestro device | | @desktop / @cross-platform | Launches JavaFX app via agent JAR, closes | | @database / @cross-platform | Connects DB before, disconnects after |

Project Structure

conductor/
├── src/                   Framework library
│   ├── drivers/           WebDriver, ApiDriver, MaestroDriver, DatabaseDriver
│   ├── hooks/             Tag-driven Before/After hooks
│   ├── pages/             BasePage to extend
│   ├── world/             ConductorWorld (Cucumber World subclass)
│   └── support/           Logger, retry helpers
├── config/                Environment configs (default/dev/staging)
├── example/               Working multi-platform example project
├── apps/                  Sample apps under test
│   ├── mobile/            Flutter Android todo app
│   ├── desktop/           JavaFX todo app
│   └── server/            Express server + web UI + REST API
├── docs/                  User guide, API docs
└── docker-compose.yml     PostgreSQL for the example server

Running the Example

# 1. Start PostgreSQL + Express server
docker compose up -d
cd apps/server && npm start &

# 2. Run all scenarios except mobile (no device required)
cd example
npx cucumber-js --tags 'not @mobile' \
  --require-module ts-node/register \
  --require-module tsconfig-paths/register \
  --require '../src/hooks/index.ts' \
  --require 'step-definitions/**/*.ts' \
  --format progress --format allure-cucumberjs/reporter \
  features/**/*.feature

# 3. Open the Allure report
npm run report && npm run report:open

For mobile and desktop, see docs/USER_GUIDE.md.

Documentation

Contributing

See CONTRIBUTING.md.

License

MIT © Nourreddine Houari