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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@testgorilla/tgo-ui

v3.14.13

Published

# Test app

Readme

TestGorilla UI Library

Test app

To see the updates of the library in the client app, use commands below from package.json

  • build the updated version of canopy-ui with build:tgo-ui (ng build tgo-ui)
  • restart the client app with start:client (ng serve)

Foundations

  • Typography
  • Colors

Components

  • Alert Bars
    • Alert Banner
    • Banner Actions
    • Snackbar
  • Button
  • Elevation Shadow
  • Dialog
    • Confirm Dialog
    • Custom Dialog
  • File Upload
  • Forms
    • Checkbox
    • Datepicker
    • Dropdown
    • Input Field
    • Radio
  • Icon
    • Icon + Label
  • Logo
  • Overflow Menu
  • Progress Bar
  • Tag
  • Tooltip

Deprecated

  • Card
  • Create Account
  • Create Password
  • Forgot Password
  • Label
  • Login
  • NavBar
  • Navigation
  • Paginator
  • Table

Visual Regression Testing

The project uses Playwright for visual regression testing to ensure UI components maintain their visual appearance across changes. Visual tests automatically capture screenshots of all Storybook stories and compare them against stored snapshots.

Commands

# Run visual tests
npm run visual-test

# Update snapshots when visual changes are intentional
npm run visual-test:update-snapshots

How It Works

  1. Build Phase: Storybook is built (npm run build-storybook) creating static files
  2. Docker Execution: Tests run in a Linux container using mcr.microsoft.com/playwright:v1.55.1 for consistency
  3. Server Setup: HTTP server serves Storybook static files on port 4200
  4. Test Execution: Automatically discovers and tests all stories from Storybook's index.json
  5. Screenshot Comparison: Compares current screenshots against stored snapshots

Docker Configuration

The system uses Docker Compose with two services:

  • visual-tests: Runs tests and compares with existing snapshots
  • update-snapshots: Updates snapshots when visual changes are expected

Both services:

  • Use official Microsoft Playwright image (mcr.microsoft.com/playwright:v1.55.1)
  • Mount project directory and install dependencies
  • Start HTTP server and wait for Storybook availability
  • Execute tests with Desktop Chrome viewport (1920x1200, 2x device scale)

Cross-Platform Consistency

Visual tests run in Docker to ensure:

  • Consistent font rendering across operating systems
  • Identical browser behavior regardless of host OS
  • Reproducible results in CI/CD environments
  • Linux-based snapshots that match production environments

Troubleshooting

  • Tests failing locally: Run npm run visual-test:update-snapshots if changes are intentional
  • Font rendering differences: Always use Docker commands for consistency
  • Timeout issues: Server waits up to 60 seconds for Storybook to be ready
  • Memory issues: Docker services configured with 4GB heap size