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

codowave

v1.1.4

Published

AI-powered code analysis and bug detection CLI

Downloads

2,712

Readme

E2E Tests

This directory contains end-to-end tests for the webhook service, configured to run against the Dokploy Redis instance at 10.0.1.9.

Prerequisites

  • Node.js 20+
  • Access to Redis at 10.0.1.9:6379
  • All dependencies installed (npm install)

Quick Start

# Run all E2E tests
npm run test:e2e

# Run specific test file
npx vitest run e2e/webhook/webhook.test.ts

# Watch mode (re-run on file changes)
npm run test:e2e:watch

Configuration

E2E tests use environment variables for Redis connection:

| Variable | Default | Description | | ----------------------- | ---------- | ----------------------- | | REDIS_HOST | 10.0.1.9 | Redis server IP | | REDIS_PORT | 6379 | Redis server port | | REDIS_CONNECT_TIMEOUT | 5000 | Connection timeout (ms) | | REDIS_COMMAND_TIMEOUT | 5000 | Command timeout (ms) |

Local Overrides

To override settings for local development:

# Create local override file
cp .env.test .env.test.local

# Edit .env.test.local with your settings
REDIS_HOST=localhost
REDIS_PORT=6379

The .env.test.local file is gitignored and won't be committed.

Test Structure

e2e/
├── config/
│   └── redis.config.ts      # Redis configuration with validation
├── helpers/
│   ├── redis-client.ts      # Redis client factory
│   └── test-isolation.ts    # Test data cleanup utilities
├── setup/
│   └── redis-setup.ts       # Vitest setup/teardown
└── webhook/
    └── webhook.test.ts      # Webhook E2E tests

Test Isolation

Tests use prefixed keys to ensure isolation:

e2e:test:{test-id}:{timestamp}:{key-suffix}

All test data is automatically cleaned up after each test.

Troubleshooting

Connection refused

# Verify Redis is accessible
redis-cli -h 10.0.1.9 -p 6379 ping

# Should return: PONG

Tests timing out

Check network latency to Redis and adjust timeouts in .env.test:

REDIS_CONNECT_TIMEOUT=10000
REDIS_COMMAND_TIMEOUT=10000

Flaky tests

Enable retry mode:

npx vitest run e2e/ --retry=3

CI/CD Integration

Tests are designed to run in CI/CD pipelines with the configured Redis host:

# Example GitHub Actions
- name: Run E2E Tests
  env:
    REDIS_HOST: 10.0.1.9
    REDIS_PORT: 6379
  run: npm run test:e2e