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

lighthouse-mariner

v3.1.0

Published

A command line tool for testing and comparing multiple URLs with Google Lighthouse

Downloads

31

Readme

Lighthouse Mariner

A command line tool for testing multiple URLs with Google Lighthouse

Install

$ npm install -g lighthouse-mariner

Table of Contents


Site Scan Tool

Usage

$ lighthouse-mariner --help
  Usage: cmd [options]

Options:
  -s, --sites [sites]            a comma delimited list of site urls to analyze with Lighthouse
  -f, --file <path>              an input file with a site url per-line to analyze with Lighthouse
  -p, --passes <number>          How many passes should be run on each route to generate each average score? (default: 1)
  -o, --output-directory <path>  Directory to save output files (default: "./lighthouse-mariner-reports")
  -d, --desktop-only             Only run using desktop profile
  -m, --mobile-only              Only run using mobile profile
  -q, --quiet                    Hide all console output
  -V, --version                  output the version number
  -h, --help                     display help for command

How to

Use --sites flag

$ lighthouse-mariner -s http://www.google.com

Multiple sites:

$ lighthouse-mariner -s http://www.google.com,http://www.yahoo.com

Use --file usage

Create a text file containing each URL you would like to audit (1 per line). This example can be found in the examples/ folder of the repo.

url-list.txt:

https://www.google.com
https://www.yahoo.com
https://www.msn.com
https://www.bing.com

To run audit on files:

$ lighthouse-mariner -f ./url-list.txt

Output

Console

If the -q flag is not used, the console will show the progress of each scan as it completes.

The console will also display a table of the results when completed.

Folder

A folder is generated in your working directory (if it doesn't already exist), named lighthouse-mariner-reports/. All output files will be created here.

Use the -o flag and specify a directory to change the output directory.

JSON

As the script runs lighthouse on each URL, it will add the latest scan info to a audit-{TIMESTAMP}.report.json file. (If the script ends prematurely for any reason, the latest data will be available in this file.)

HTML

When the script completes, it will create an HTML report: audit-{TIMESTAMP}.report.html.

Example


Compare Tool

The compare tool can be used to monitor progress of routes over time. This tool will accumulate all scan data from a directory, group it by each route, and generate an output HTML file that will display the differences of the scans over time via graphs and tables.

Usage

$ lighthouse-mariner compare --help
Usage: cmd compare [options]

compare sites scans over time to monitor progress

Options:
  -f, --folder <path>  name of a absolute path, relative path, or name of a directory within /lighthouse-mariner-reports folder
  -V, --version        output the version number
  -h, --help           display help for command

Example output

License

ISC