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

@testla/create-screenplay

v1.1.0

Published

Scaffold tool for testla-screenplay projects

Readme

🎭 Create Testla Screenplay - CLI tool for quickly creating Testla Screenplay projects with Playwright 🎭

This package provides an initializer to interactively and automatically set up new Testla Screenplay projects with Playwright.

Usage

You can create a new Testla Screenplay project using one of the following commands:

# In the current directory (recommended: create an empty directory first)
npm init @testla/screenplay
npx @testla/create-screenplay
yarn create @testla/screenplay
pnpm create @testla/screenplay

The tool uses the current directory name as the project name and sets up the project structure there.

Example:

mkdir my-tests
cd my-tests
npm init @testla/screenplay
# Project name is "my-tests"

What happens when you run it?

  1. Interactive configuration (prompts):

    • Name of the test directory (default: tests)
    • Base URL of the application under test
    • Browser (chromium, firefox, webkit)
    • Headless mode (default: true)
    • Reporter (testla-reporter, html, junit, json, list, dot)
  2. Project structure is created:

    <project-directory>/
    ├── <tests>/                  # Test files (e.g. example.spec.ts)
    ├── screenplay/
    │   ├── tasks/                # Example task
    │   ├── actions/              # (empty)
    │   ├── questions/            # (empty)
    │   └── screens/              # Example screen
    ├── fixtures/                 # Test actor
    ├── playwright.config.ts      # Playwright configuration
    ├── .env                      # Environment variables
    ├── .gitignore                # Git ignore
    ├── README.md                 # Project documentation (generated)
    └── package.json
  3. Dependencies are installed:

    • @playwright/test
    • @testla/screenplay-playwright
    • dotenv
    • @types/node (dev)
  4. Configuration and example files are generated:

    • Playwright configuration (playwright.config.ts)
    • .env file with your settings
    • Example test, demo task, demo screen, fixtures
    • Project-specific README (replaces this file in the target project)
  5. package.json is updated:

    • Script: testnpx playwright test

Features

  • 🛠️ Interactive setup with sensible defaults
  • 📁 Automatic folder structure following the Screenplay pattern
  • 🚀 Ready to use with example code and configuration
  • 🌐 Multi-browser support (Chromium, Firefox, WebKit)
  • 📚 Generates a README for the new project

Example output after successful setup

✔ Success! Created a Testla Screenplay project at /path/to/project

We suggest that you begin by typing:

npm test
Runs the end-to-end tests.

And check out the following files:
- ./<tests>/example.spec.ts - Example test
- ./fixtures/user.ts - Definition of the Actor
- ./screenplay/tasks/demo-task.ts - Example task
- ./screenplay/screens/demo-screen.ts - Example screen
- ./playwright.config.ts - Playwright configuration
- ./.env - Environment variables

✨ More info: https://github.com/testla-project/testla-screenplay-playwright-js/tree/main/docs ✨

🚀 Discord: https://discord.gg/MDRjCH3v 🚀

Happy hacking! 🎭

Requirements

  • Node.js 18.0.0 or higher
  • npm, yarn, or pnpm

Links

License

MIT