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

@corva/dc-platform-shared

v0.60.0

Published

A library to share internal DC platform specific code

Readme

corva-dc-platform-shared

A repository to share Dev Center platform code

Contributing Guide

Quick Start

  1. Branch Setup

    git checkout develop
    git pull
    git checkout -b feature/your-feature   # or fix/your-fix
  2. Development

    • Write code
    • Add tests
    • Run:
      yarn install
      yarn lint
      yarn test
  3. Create PR

    • Push to your branch
    • Create PR to develop
    • PR title must follow conventional commits:
      feat: add user authentication
      fix: resolve login error
      feat!: change API response format

Branch Strategy

  • develop - main development branch
  • feature/* - new features
  • fix/* - bug fixes
  • No direct commits to develop

Release Process

  1. Get your PR merged to develop
  2. Release Please automatically:
    • Creates release PR
    • Updates version based on commits
    • Generates changelog
  3. Merge the Release Please PR
  4. System automatically:
    • Creates git tag
    • Runs E2E tests
    • Publishes to NPM

Version Bumping

  • Automatic based on PR titles:
    • fix:0.0.X
    • feat:0.X.0
    • feat!: or BREAKING CHANGE:X.0.0
  • Never modify version manually

CI Checks

Your PR must pass:

  • Linting
  • Unit tests
  • E2E tests (feature/fix branches)
  • PR title validation
  • Code review

Remember: The key is writing good code and using correct commit conventions - the release process is automated!