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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@estruyf/github-actions-reporter

v1.10.0

Published

GitHub Actions reporter for Playwright

Readme

GitHub Actions Reporter for Playwright

This action reports test results from Playwright to GitHub summaries.

Installation

Install from npm:

npm install @estruyf/github-actions-reporter

Usage

You can configure the reporter by adding it to the playwright.config.js file:

import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['list'],
    ['@estruyf/github-actions-reporter']
  ],
});

More information on how to use reporters can be found in the Playwright documentation.

Configuration

The reporter supports the following configuration options:

| Option | Description | Default | | --- | --- | --- | | title | Title of the report. Use an empty string ("") to remove the heading. | Test results | | useDetails | Use details in summary which creates expandable content | false | | showAnnotations | Show annotations from tests | true | | showAnnotationsInColumn | Shows annotations from tests but in a column. To enable showAnnotations must be set to true | false | | showTags | Show tags from tests | true | | showError | Show error message in summary | false | | includeResults | Define which types of test results should be shown in the summary | ['pass', 'skipped', 'fail', 'flaky'] | | quiet | Do not show any output in the console | false | | showArtifactsLink | Show a link to the artifacts section in the workflow overview | false | | azureStorageUrl | URL to the Azure Storage account where the screenshots are stored (optional) | "" | | azureStorageSAS | Shared Access Signature (SAS) token to access the Azure Storage account (optional) | "" |

To use these option, you can update the reporter configuration:

import { defineConfig } from '@playwright/test';
import type { GitHubActionOptions } from '@estruyf/github-actions-reporter';

export default defineConfig({
  reporter: [
    ['@estruyf/github-actions-reporter', <GitHubActionOptions>{
      title: 'My custom title',
      useDetails: true,
      showError: true
    }]
  ],
});

Example without details

Example without details

Example with details

Example with details

Showing result attachments

If you want to show attachments like when you use pixel matching, you need to provide the configuration for the blob service where the images will be stored.

[!NOTE] GitHub does not have an API to link images to the summary. Therefore, you need to store the images in a blob storage service and provide the URL to the images.

[!IMPORTANT] To show the attachments, you need to make sure to enable showError as well.

Example with attachments

Azure Blob Storage

If you are using Azure Blob Storage, you need to provide the azureStorageUrl and azureStorageSAS configuration options.

Follow the next steps to get the URL and SAS token:

  • Go to your Azure Portal
  • Navigate to your storage account or create a new one
  • Navigate to data storage > containers
  • Create a new container. Set the access level to Blob (anonymous read access for blobs only)
  • Open the container, and click on Shared access signature
  • Create a new shared access signature with the following settings:
    • Allowed permissions: Create
    • Expiry time: Custom (set the time you want)
    • Allowed protocols: HTTPS only
  • Click on Generate SAS and URL
  • Copy the Blob SAS token, this will be your azureStorageSAS value
  • Copy the Blob service URL and append the container name to it, this will be your azureStorageUrl value. Example: https://<name>.blob.core.windows.net/<container-name>.
  • Update the playwright.config.js file with the following configuration:
import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['@estruyf/github-actions-reporter', {
      showError: true,
      azureStorageUrl: 'https://<name>.blob.core.windows.net/<container-name>',
      azureStorageSAS: '<your-sas-token>'
    }]
  ],
});

Visitors