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

lighthouse-plus

v1.0.3

Published

Make performance and accessibility analysis simple to run, even in environments with access constraints like login pages.

Downloads

4

Readme

Ligthhouse plus

Thanks to an intuitive and easy-to-use CLI tool, Lighthouse plus allows you to easily check for accessibilty, performance and seo issues inside your app - no matter how complex it is.

Installation

Simply install using your node package manager of choice:

npm install -g lighthouse-plus

How to start ?

Create a lighthouse-plus.yaml file at the root of your application. This file will hold any most of the configuration and specification to run the desired analysis. Here is a template :

check_for:
  - performance
  - accessibility
  - seo
before_each:
  at: https://example.org/login
  act:
    - on: "#username"
      do: "type"
      value: "user123"
    - on: "#password"
      do: "type"
      value: "passwd"
    - on: "#submit"
      do: "click"
analysis:
  dashboard-page:
    at: "https://example.org/dashboard"
    setup:
      - on: "#active-all"
        do: "click"

The example above will log a user on the https://example.org/login page using the user123/passwd credentials. It will them go to https://example.org/dashboard, click on the element associated with the #active-all selector and run a performance, an accessibility and a seo analysis.

API Reference

CLI Parameters

| Argument | Alias | Details | Value type | Default | | -------------- | ----- | ------------------------------------------------------------------------------------------------------------- | ---------- | ------------------------ | | headless | h | Allow the browser to start as headless. This requires for the machine to have the appropriate configuration | boolean | true | | output | o | The target output directory | string | lighthouse | | chromium-bin | c | A reference to the chrome executable to use to execute Ligthhouse. | string | Use system configuration | | config-file | f | The path to the configuration file | string | ligthhouse.yaml |

Ligthhouse plus configuration file format

| Property | Details | Value type | Required | Default | | ------------- | --------------------------------------------------------------- | ------------------------------------------------------ | -------- | ------- | | check_for | The list of the analysis type to run. | performance|accessibility|seo|best-pratices | No | All | | before_all | The process to execute at the very start of the process | LifecycleHooks | No | | | before_each | The process to execute before each analysis | LifecycleHooks | No | | | after_all | The process to execute at the very end of the process | LifecycleHooks | No | | | after_each | The process to execute after each analysis | LifecycleHooks | No | | | analysis | The analysis configuration with the list of elements to analyse | Map<String,Analysis> | Yes | |

Lifecycle hooks reference

| Property | Details | Value type | Required | Default | | -------- | ------------------------------------------------------------------------------------------------ | --------------------------------- | -------- | ------- | | at | The URL from where to execute the different actions. If same as current URL, the page may reload | string | Yes | | | act | A list of action that needs to be performed. | Action[] | Yes | |

Analysis reference

| Property | Details | Value type | Required | Default | | ----------- | ------------------------------------------------------------------------------------------------ | --------------------------------- | -------- | ------- | | at | The URL from where to execute the different actions. If same as current URL, the page may reload | string | Yes | | | setup | Extras actions to perform before running the analysis | Action[] | No | | | tearsdown | Extras actions to perform before executing the next analysis | Action[] | No | |

Action reference

| Property | Details | Value type | Required | Default | | -------- | -------------------------------------------------------------------------------- | ----------------- | -------- | ------- | | on | The selector associated with the target element | string | Yes | | | do | The action to perform | click | type | Yes | | | value | The value to enter when using the type action. Ignore for the click actions. | string | No | '' |