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

eight-rnd-ops

v0.2.3

Published

Infrastructure code to manage the R&D AWS account. Published as an npm package consumed by service repos.

Readme

eight-rnd-ops

Infrastructure code to manage the R&D AWS account. Published as an npm package consumed by service repos.

Stacks

  • rnd-ecs — ECS Fargate cluster, shared private ALB, Route53 DNS
  • anyscale-private-v2 — Anyscale cloud eight-rnd-anyscale (cld_j15ib9rk6a52nkvw7hgmp34t89), private subnets only, VPN-gated
  • anyscale-private(deprecated) Anyscale cloud v1 eight-anyscale-production, public subnets. Migration to v2 complete — pending resource cleanup (without full stack teardown to protect VPC)

Commands

npm run build                   # Build after code changes
npx cdk synth <stack>           # Generate CloudFormation template
npx cdk diff <stack>            # Preview changes (safe, read-only)

Never run cdk deploy without explicit approval. Deployments are done manually.

Library

The cdk-lib/ directory is published as an npm package (eight-rnd-ops). Service repos consume it for shared constructs:

  • EightRndServiceConstruct — Fargate service with ALB routing, Datadog logging, secrets
  • EightRndWorkerConstruct — Background worker (no ALB listener), Datadog logging, secrets

Anyscale Cloud Setup

Deploy

  1. cdk deploy anyscale-private-v2
  2. Apply MemoryDB parameter fix (CloudFormation ignores parameters on CREATE):
    aws memorydb update-parameter-group --profile anyscale \
      --parameter-group-name <cloudId>-memorydb-pg \
      --parameter-name-values "ParameterName=maxmemory-policy,ParameterValue=allkeys-lru"
  3. Register cloud with Anyscale — see cdk-scripts/register_anyscale_cloud.sh

Post-registration

After anyscale cloud register, Anyscale adds an ExternalId condition to the access role trust policy. This is expected — the CDK stack creates the role without ExternalId, and Anyscale updates it with the cloud ID during registration.

Current cloud: eight-rnd-anyscale / cld_j15ib9rk6a52nkvw7hgmp34t89

ECS Service Migration (Private ALB)

All services on eight-rnd-ops >= 0.2.0 route through the private (internal) ALB. The public ALB is deprecated and will be removed once all services are migrated.

To migrate a service:

  1. Bump eight-rnd-ops to 0.2.1+ in the service's cdk/package.json
  2. Run npm install && npm run build in the cdk/ directory
  3. cdk diff to verify the ALB routing change
  4. Deploy