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

@cuginoale/paxe

v0.4.18

Published

Puppeteer & Axe ♿ testing framework

Downloads

17

Readme

___           ___
|__)  /\  \_/ |__
|    /--\ / \ |___            
-----------------------------------
Puppeteer & Axe ♿ testing framework

Paxe is an automated accessibility testing tool based on Puppeteer and Axe. It runs from the command line and generates HTML reports for each page and each viewport analysed.

It is still a WIP, feedbacks and contributions are highly appreciated!

Get started

For a quick test you can run:

- $> npx @cuginoale/paxe

If you plan to use it frequently or if it's going to be part of your workflow:

- $> npm i -g @cuginoale/paxe
- $> cd path/to/your/project/folder
- $> paxe

On first run Paxe will look for the .paxerc in the current folder. If it can't find it, Paxe wizard will guide you through the steps to create a basic configuration file (still w.i.p.)

The .paxerc file is basically a JSON object, structured as follows:

{
  "default": {
    "viewports": [
      {
        "width": "xx",
        "height": "yy"
      },
      ...
    ],
    "outputFolder": "output",
    "authenticate": {
      "username": "user",
      "password": "pwd"
    }
  },
  "urls": {
    "friendly_name":{
      "url":"http://my_target_website",
      "options":{
        "actions":[
          {"click":"button.sc-fONwsr.dRSxZO"},
          {"waitFor": 1000}
        ],
        "viewports": [
          {
            "width": "xx",
            "height": "yy"
          },
          ...
        ],
        "authenticate": {
          "username": "user",
          "password": "pwd"
        }
      }
    },
    ...
}

default contains the settings applied to all the urls to test. Url specific settings can be defined in the url options section.

The options section for each url is optional and can contain:

  • actions to perform before the test is run
  • specific vieports
  • basic HTTP authentication settings

The actions available are all the actions Puppeteer is capable to run on the page object see relevant doc

Cli

$> paxe --help

Usage: paxe [<option>]

Options:
  --help         Show help                                             [boolean]
  --version      Show version number                                   [boolean]
  --runOnly, -o  Comma separated list of URLs (friendly names)

To test only some of the URLs listed in the .paxerc file use --runOnly or -o followed by the friendly name of the urls to test:

$> paxe -o site1,site2,site3

Report example: