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

wp-pa11y

v1.0.0

Published

Run [pa11y](https://github.com/pa11y/pa11y) to each page on your sitemaps.

Downloads

2

Readme

WP-Pa11y

Run pa11y to each page on your sitemaps.

Installation instructions

As a global npm package

TBA

As a project npm dependency

TBA

git Clone

  1. Clone the repository to your chosen location (choose wisely, this will be the folder you will be running wp-pa11y from)
  2. Run npm install inside the folder
  3. Set up your sitemaps.txt (see section "Configuration")
  4. Run the app (see section "Running the app")

Configuration

wp-pa11y reads sitemaps from one of two locations.

You can use either sitemaps.txt file or wp-pa11y key in the project package.json file (examples below).

wp-pa11y prefers sitemaps.txt to package.json, so use one of them to avoid confusion.

Using sitemaps.txt

Create file sitemaps.txt and add each sitemap.xml to its own line.

https://example.com/sitemap.xml
https://subdomain.example.com/sitemap.xml

If you are still confused, see sitemaps.txt.example.

Using package.json

Add wp-pa11y array to your project root package.json and add sitemaps as array items.

{
  "name": "your-project",
  "version": "x.y.z",
  "dependencies": {},
  "devDependencies": {},
  "wp-pa11y": [
    "https://example.com/sitemap.xml",
    "https://subdomain.example.com/sitemap.xml"
  ]
}

Running the app

Using wp-pa11y

Depending on installation method, the command might be node wp-pa11y.js or node node_modules/.bin/wp-pa11y.

Running without any options' app checks sitemaps and outputs reports to the CLI.

To see all available options and arguments run wp-pa11y --help.

From git clone (using make)

| command | Description | |-------------|--------------------------------------------------------| | make html | Generates HTML reports to ./output/{domain}/ folder. | | make cli | Outputs reports to cli. |

Contributors

See up-to-date list of project contributors.

License

MIT License