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-plugin-headings

v1.0.1

Published

wSEO.pw Lighthouse plugin for custom heading audits

Readme

lighthouse-plugin-headings

Плагин для Lighthouse, добавляющий пользовательскую категорию Headings с аудитами структуры заголовков:

  • H1 missing — проверка наличия <h1> в исходном HTML
  • H1 multiple — обнаружение более одного <h1>
  • H1 added by JS — (будет) выявление добавления <h1> скриптом
  • H1 updated by JS — (будет) проверка изменения/удаления <h1> после рендеринга
  • H1 not first header — первый заголовок должен быть <h1>
  • HN minus 2 after hN — проверка перепрыгивания уровней заголовков
  • Heading is empty — поиск пустых тегов заголовков
  • H2 missing — проверка наличия <h2> в исходном HTML

Установка

Через npm:

npm install -g lighthouse-plugin-headings
# или в проект
npm install --save-dev lighthouse-plugin-headings

Запуск

lighthouse <URL> \
  --plugins=lighthouse-plugin-headings \
  --view
  • --view — автоматически откроет HTML-отчёт в браузере.
  • По умолчанию в отчёте появится категория Headings с вашими аудитами.

Для запуска только вашей категории:

lighthouse <URL> \
  --plugins=lighthouse-plugin-headings \
  --only-categories=headings \
  --view

Использование в CI / автоматизация

Варианты:

  • Lighthouse CI
    Добавьте в lighthouserc.js плагин:
    module.exports = {
      ci: {
        collect: {
          url: ['https://example.com'],
          numberOfRuns: 1,
          settings: {
            plugins: ['lighthouse-plugin-headings']
          }
        }
      }
    };
  • Программный запуск
    const lighthouse = require('lighthouse');
    const chromeLauncher = require('chrome-launcher');
    
    (async () => {
      const chrome = await chromeLauncher.launch({chromeFlags: ['--headless']});
      const options = {port: chrome.port, plugins: ['lighthouse-plugin-headings']};
      const runnerResult = await lighthouse('https://example.com', options);
      console.log('Score:', runnerResult.lhr.categories.headings.score);
      await chrome.kill();
    })();

Contributing

  1. Сделайте форк репозитория
  2. Создайте новую ветку feat-my-audit
  3. Добавьте файл вашего аудита в папку audits/
  4. Зарегистрируйте его в plugin-headings.js (в секциях audits и category.auditRefs)
  5. Откройте PR

Лицензия

MIT © Michael Kozhevnikov