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

@guidepup/setup

v0.24.1

Published

CLI for configuring environments and install screen reader assets for Guidepup.

Readme

@guidepup/setup

Documentation

macOS Sonoma Support macOS Sequoia Support macOS Tahoe Support Windows Server 2022 Support Windows Server 2025 Support

The @guidepup/setup CLI enables automation for VoiceOver on macOS and NVDA on Windows.

Quick start

# Set up machine once for screen reader automation
npx @guidepup/setup setup

# In project directory install Guidepup
npm install @guidepup/guidepup

# In project directory install required screen reader assets
npx @guidepup/setup install

Environment setup

The setup CLI command configures your operating system for screen reader automation and only needs to be run once per machine:

npx @guidepup/setup setup

CI

If you are running the setup CLI command in CI/CD, it is recommended to add the --ci flag to prevent prompts for manual interaction:

npx @guidepup/setup setup --ci

macOS

If you are running this command locally you may need to take some manual steps to complete setup by following the manual VoiceOver setup documentation.

Ignoring TCC database updates

If updating the TCC.db is not possible (due to enabled System Integrity Protection) or not required for your macOS setup, you can skip database updates by using the --macos-ignore-tcc-db flag:

npx @guidepup/setup setup --macos-ignore-tcc-db

[!NOTE] If the necessary permissions have not been granted by other means, using this flag may result in your environment not being set up for reliable screen reader automation.

[!WARNING] For system TCC.db updates you must first disable System Integrity Protection (SIP). This comes with serious security implications, so please first refer to the Apple documentation for more details before taking any action. Consider whether you are able to use alternative manual setup steps for configuration before exploring this option further.

SIP only needs to be disabled while the required changes are being made. Re-enable SIP once the setup CLI command has completed.

Recording

If you are encountering errors in CI for macOS you can pass a --macos-record flag to the command which will output a screen-recording of the setup to a ./recordings/ directory:

npx @guidepup/setup setup --ci --macos-record

Installing screen reader assets

Each version of Guidepup requires specific screen reader assets to execute correctly.

Install the default supported screen reader assets with one command from your project directory:

npx @guidepup/setup install

The install CLI command uses your project's installed @guidepup/guidepup version to determine which screen reader assets to install.

New Guidepup releases may update the required screen reader assets. If you update Guidepup, rerun the install CLI command to install the latest supported screen reader assets.

You can install a specific screen reader by providing additional arguments to the install CLI command:

# Install VoiceOver
npx @guidepup/setup install voiceover

# Install NVDA
npx @guidepup/setup install nvda

Screen reader options include:

  • voiceover on macOS (default)
  • nvda on Windows (default)

Managing screen reader assets

By default Guidepup downloads screen reader assets into the operating system's standard cache directory:

  • ~/.cache/guidepup/ on Linux
  • ~/Library/Caches/guidepup/ on macOS
  • %USERPROFILE%\AppData\Local\guidepup\ on Windows

You can override the default cache directory using an environment variable:

GUIDEPUP_SCREEN_READERS_PATH=$HOME/guidepup npx @guidepup/setup install

Unused screen reader cleanup

Guidepup tracks which projects use each installed screen reader asset. When an asset is no longer referenced by any project, it is automatically removed the next time the install CLI command runs.

Installing behind a proxy

Guidepup screen readers are installed directly from GitHub release URLs. If you are using a proxy you can use an environment variable to define the proxy URL:

HTTPS_PROXY=https://192.0.2.1 npx @guidepup/setup install

Global install

You can install the CLI globally:

npm install -g @guidepup/setup

After which you can access the CLI directly through the guidepup command:

guidepup setup
guidepup install

Powerful tooling

Check out some of the other Guidepup modules:

Resources