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

@leanix/reporting-dimensions

v0.2.60

Published

A TypeScript library that implements clustering and views for reports.

Readme

reporting-dimensions

A TypeScript library that implements clustering and views for reports.

Connect locally with report

  • build locally
  • replace version in the report's package.json with e.g. "@leanix/reporting-dimensions": "~/dev/reporting-dimensions"

see slack: https://leanix.slack.com/archives/C98RHJZPU/p1694418724394299

Release Process

This package uses automated publishing - merging to main automatically publishes to npm when the version changes.

How It Works

  1. Version Detection: On every push to main, CI compares package.json version with npm registry
  2. Auto-Publish: If version is new → publishes to npm automatically
  3. Skip if Same: If version already exists → skips publishing (no errors)

Releasing a New Version

Option 1: Pre-push Hook (Recommended)

When you push, a pre-push hook prompts you:

🚀 Release Check
Will these changes need a release?
[y] Yes - bump version now
[n] No - skip release
[l] Later - ask me next push

Choose y and select version type (patch/minor/major). The hook automatically:

  • Bumps the version in package.json
  • Commits the change
  • Proceeds with the push

Option 2: Manual Version Bump

  1. Update version in package.json following Semantic Versioning
  2. Commit the change
  3. Push/merge to main

Skipping Release Checks

For branches that don't need releases (e.g., documentation-only):

  • Choose n at the pre-push prompt, or
  • Create a .no-release file (git-ignored)

Verification

After merging, check the trigger-release workflow:

  • ~60s run = successful publish
  • ~30s run = version skipped (already published)