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

axe-browser-reporter

v1.1.4

Published

In-browser Axe reporter that prompts as soon as it finds an accessiblity issue

Downloads

28

Readme

axe-browser-reporter

code style: prettier Renovate enabled npm version Downloads CircleCI

Description

Axe reporter injected in the browser page if it detects any accessibility issue.

This project is made to make the accessibility development a top priority. As soon as an a11y rule is broken, the popup will simply appear and let you know how you can fix it. We strongly rely on axe-core

Installation

npm i axe-browser-reporter

Usage

In order for the plugin to kick in, make sure that your global environment variable process.env.NODE_ENV does equal 'development'. Otherwise, axe-browser-reporter won't run at all.

In your project, import axe-browser-reporter at the root of your project (e.g. an index.(js|ts) file).

import bootstrap from "axe-browser-reporter";
// Any setup code at root level of your app
bootstrap();

Options

Some options can be passed to bootstrap in order to tweak axe under the hood

import bootstrap from "axe-browser-reporter";

// Default values
bootstrap({
  allowlist: [],
  runIf: () => process.env?.NODE_ENV === "development",
});

allowlist

If there are rules you want axe-browser-reporter not to notify you about, you can specify them in an array of string like such. The argument is the id given from axe. The full list can be found here

import bootstrap from "axe-browser-reporter";

// Will ignore color-contrast and frame-tested a11y rules
bootstrap({
  allowlist: ["color-contrast", "frame-tested"],
});

runIf

If you want to change the condition on wheter to run axe-browser-reporter or not, you can specify a runIf attribute. Its signature is () => boolean

import bootstrap from "axe-browser-reporter";

const myBoolean = randomCondition ? true : false;

bootstrap({
  runIf: () => myBoolean,
});