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

playwright-lighthouse-report

v1.0.0

Published

Playwright Lighthouse Audit

Downloads

6

Readme

Lighthouse Playwright - NPM Package

Installation

You can add the @silencei/playwright-lighthouse library as a dependency (or dev-dependency) in your project

$ yarn add -D @silencei/playwright-lighthouse
# or
$ npm install --save-dev @silencei/playwright-lighthouse

In your code

After completion of the Installation, you can use @silencei/playwright-lighthouse in your code to audit the current page.

In your test code you need to import @silencei/playwright-lighthouse and assign a port for the lighthouse scan. You can choose any non-allocated port.

const {playAudit} = require('@silencei/playwright-lighthouse');
const playwright = require('playwright');

describe('audit example', () => {
    it('open browser', async () => {
        const browser = await playwright['chromium'].launch({
            args: ['--remote-debugging-port=9222']
        });
        const page = await browser.newPage();
        await page.goto('https://angular.io/');

        await playAudit({
            page: page,
            port: 9222
        });

        await browser.close();
    });
});

Thresholds per tests

If you don't provide any threshold argument to the playAudit command, the test will fail if at least one of your metrics is under 100.

You can make assumptions on the different metrics by passing an object as argument to the playAudit command:

const {playAudit} = require('@silencei/playwright-lighthouse');
const playwright = require('playwright');

describe('audit example', () => {
    it('open browser', async () => {
        const browser = await playwright['chromium'].launch({
            args: ['--remote-debugging-port=9222']
        });
        const page = await browser.newPage();
        await page.goto('https://angular.io/');

        await playAudit({
            page: page,
            thresholds: {
                performance: 50,
                accessibility: 50,
                'best-practices': 50,
                seo: 50,
                pwa: 50
            },
            port: 9222
        });

        await browser.close();
    });
});

If the Lighthouse analysis returns scores that are under the one set in arguments, the test will fail.

You can also make assumptions only on certain metrics. For example, the following test will only verify the "correctness" of the performance metric:

await playAudit({
    page: page,
    thresholds: {
        performance: 85
    },
    port: 9222
});

This test will fail only when the performance metric provided by Lighthouse will be under 85.

Passing different Lighthouse config to @silencei/playwright-lighthouse directly

You can also pass any argument directly to the Lighthouse module using the second and third options of the command:

const thresholdsConfig = {
    /* ... */
};

const lighthouseOptions = {
    /* ... your lighthouse options */
};

const lighthouseConfig = {
    /* ... your lighthouse configs */
};

await playAudit({
    thresholds: thresholdsConfig,
    opts: lighthouseOptions,
    config: lighthouseConfig

    /* ... other configurations */
});

Sometimes it's important to pass a parameter disableStorageReset as false. You can easily make it like this:

const opts = {
    disableStorageReset: false
};

await playAudit({
    page,
    port: 9222,
    opts
});

Generating audit reports

@silencei/playwright-lighthouse library can produce Lighthouse CSV, HTML and JSON audit reports, that you can host in your CI server. These reports can be useful for ongoing audits and monitoring from build to build.

await playAudit({
    /* ... other configurations */

    reports: {
        formats: {
            json: true, //defaults to false
            html: true, //defaults to false
            csv: true //defaults to false
        },
        name: `name-of-the-report`, //defaults to `lighthouse-${new Date().getTime()}`
        directory: `path/to/directory` //defaults to `${process.cwd()}/lighthouse`
    }
});

Sample HTML report:

screen

Before you go

If it works for you , give a Star! :star:

- Copyright © 2020- Abhinaba Ghosh