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

@a11ywatch/core

v0.8.17

Published

a11ywatch central API

Downloads

1,834

Readme

a11ywatch-core

Maintainability

Central API for A11yWatch available in REST, GraphQl, and gRPC.

Getting Started

To get started you can use docker or run on your local machine following the commands below. In order to run this repo effectively take a look at the docker compose file in the central command repo compose.

docker-compose up

or

npm i
npm run dev

Environmental variables

Project configuration below:

Emailing

To get the emailer working add the following env variables to the project.

[email protected]
EMAIL_CLIENT_ID=
EMAIL_CLIENT_KEY=

JS Scripts

In order to store javascript locally to use you need to enable the following env vars:

SCRIPTS_ENABLED=true
A11YWATCH_NO_STORE=false

Cron

Enable CRON morning and nightly jobs

A11Y_WATCH_CRON_ENABLED=true

Queue

Set the limit to number of test in parallel per run to CRAWL_QUEUE_LIMIT env var - default is set to 8. If you have kubernetes, docker swarm, or Fargate - you can increase this limit based on your chrome browser count.

Testing

In order to easily test the application we use dagger

dagger do build

LICENSE

check the license file in the root of the project.