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 🙏

© 2024 – Pkg Stats / Ryan Hefner

humpty

v0.0.2

Published

Makes sure your changelogs mention your breaking changes

Downloads

15

Readme

Humpty 🍳

Makes sure your changelogs mention your breaking changes

Build Status npm

Intro

It's really easy to make a breaking API change to your React component and forget to release it as a major version. Humpty stops this from happening by checking what's changed in your component API, and making sure it is mentioned in your changelogs.

Usage

$ humpty --oldApi 72c5c9e0 --newApi c72257 --gitRepo ~/Repos/bengummer/humpty-mock-api

🚨 Found 1 breaking API change not mentioned in git commits (72c5c9..c72257):

Default export
  - Prop type changed: "age" was string, now number

Supported APIs and changelogs

💡 This project has just started, a pluggable API/changelog system can be added to support APIs other than React. Raise an issue to discuss! Check out the Trello board for the roadmap.

Supported API detection

  • React components
    • Prop removed
    • Prop type changed
    • Prop made mandatory
    • Prop made optional

Note: React components are currently only checked in the root index.js file - this will be made more flexible soon to read the main script from package.json.

Supported changelogs

  • React components
    • Commit messages containing ${propName} prop

Installation

If you're using humpty in CI you can install it globally

$ yarn global add humpty

Or add it as a devDependency and call it via an npm script

{
  "name": "my-component",
  "scripts": {
    "humpty": "humpty ..."
  }
}
$ yarn add --dev humpty
$ yarn run humpty

Detailed usage

--oldApi

Git branch or SHA where your current public API code is stored.

--newApi

Git branch or SHA where your new public API code is stored.

--gitRepo

Path to the git repo where your source lives.

--json (optional)

Output result as JSON instead of emoji + text