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

@kavrillon/web-q5y

v1.1.2

Published

Perform web audits via Jest.

Downloads

39

Readme

Web Q5Y Checker

Testing: SEO audit, Lighthouse audit with Jest

Installation

  1. npm add @kavrillon/web-q5y or yarn add @kavrillon/web-q5y
  2. Add the test:e2e command in your package.json:
  "scripts": {
    ...
    "test:e2e": "JEST_PUPPETEER_CONFIG=node_modules/@kavrillon/web-q5y/jest-puppeteer.config.js jest test --runInBand --detectOpenHandles --verbose --config=node_modules/@kavrillon/web-q5y/jest.config.js"
  },
  1. Create a conf file at the root of your app named .q5yrc, and copy/paste the content of the sample.q5yrc file. This file will contain all your testing conf.

Testing Conf

  • command: the command that will launch the server. If not provided, no server will be launched, it will only listen for the given url.
  • loadedSelector: if provided, we will wait for this selector existence before launching tests. It is useful for testing SPAs, as the content is generated clientside.
  • url: the host url to test
  • port: the port to test
  • routes: array of the routes to test (do not put the host nor the port)
  • thresholds: for Lighthouse audit, minimum percentage to make test pass (for each category).

Tests done

SEO Audit

Check presence of meta title, description, headings, etc.

Lighthouse Audit

Pass a Lighthouse Audit via Puppeteer (a11y, perfs, best practises, seo, page speed, pwa, etc.)