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

lhci-gha

v1.4.0

Published

Lighthouse CI results reporting GitHub Action

Downloads

13,027

Readme

lhci-gha

Lighthouse CI results reporting GitHub Action

📝 Read the blog post Trying Lighthouse.

Install

Add this module as a dev dependency

# install using NPM
$ npm i -D lhci-gha
# install using Yarn
$ yarn add -D lhci-gha

Scripts

This module provides 2 command line scripts. You should use these scripts after running Lighthouse CI

# https://github.com/GoogleChrome/lighthouse-ci
- name: run Lighthouse CI
  run: |
    npm install -g @lhci/[email protected]
    lhci collect
# post performance summary and set the commit status
# https://github.com/bahmutov/lhci-gha
- name: Post performance summary 📊
  run: npx post-summary --report-filename lighthouse-results.json

post-summary

Reads the Lighthouse JSON report and writes GitHub Lighthouse job summary

Performance job summary

  • --report-filename Lighthouse performance JSON filename
  • --title summary table title

post-status

Reads the Lighthouse JSON report and sets the GitHub Commit status

Performance commit status

  • --report-filename Lighthouse performance JSON filename
  • --owner GitHub repo owner, like `bahmutov
  • --repo GitHub repo name, like web-performance-example
  • --commit Commit to set the status on
  • --target-url Link to add to the commit status, usually to the job

Usually for pull requests, you would use the head commit SHA

- name: Post performance commit status ✅
  run: |
    npx post-status --min 90 \
      --report-filename lighthouse-results.json \
      --owner bahmutov --repo web-performance-example \
      --commit ${{ github.event.pull_request.head.sha || github.sha }} \
      --target-url "${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
  env:
    PERSONAL_GH_TOKEN: ${{ secrets.PERSONAL_GH_TOKEN }}

post-comment

Posts or updates a performance comment on specific issue or pull request

Posted comment

  • --report-filename Lighthouse performance JSON filename
  • --owner GitHub repo owner, like `bahmutov
  • --repo GitHub repo name, like web-performance-example
  • --issue pull request or issue number to comment on
  • --title the start of the comment body, like "Performance metric"

This script checks all comments on PR to find the one that starts with "**${title}" text, if found it updates it. Otherwise, it posts a new comment.

- name: Post performance comment 📝
  if: github.event.pull_request
  run: |
    npx post-comment \
      --report-filename lighthouse-results.json \
      --owner bahmutov --repo web-performance-example \
      --pr ${{ github.event.pull_request.number }}
  env:
    PERSONAL_GH_TOKEN: ${{ secrets.PERSONAL_GH_TOKEN }}

Examples

Debugging

This module uses debug to output verbose messages. To see debug logs, run with the DEBUG environment variable set to lhci-gha

$ DEBUG=lhci-gha ...

Small print

Author: Gleb Bahmutov <[email protected]> © 2023

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2023 Gleb Bahmutov <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.