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

nothing-major

v1.1.1

Published

Ensures that you've marked your breaking change commits.

Downloads

10

Readme

Nothing Major

Ensures that you've marked your breaking change commits.

Commitizen friendly

NPM

Usage

Right now, this assumes that you're using the Angular commit message format. In the future, this may be configurable.

$ nothing-major -b 'build script' -t 'test script' [[test files]]

This will do the following:

  1. Check and see if you've already noted that the current commit has breaking changes.
  2. Creates a temporary directory.
  3. Checks out your code into a git-worktree in the temporary directory.
  4. Runs the supplied build script.
  5. Checks out the test files from the previous commit.
  6. Runs the supplied test script, exiting cleanly if it passes.
  7. Cleans up the temporary directory and the git worktree.

For an NPM project, this script may look like:

$ nothing-major -b 'npm install' -t 'npm test' test/*

The intention is that this would be setup to run as a post-commit hook. The build script runs a bit slowly right now (which I'm guessing has to do with building in a fresh directory), so it hasn't seemed practical yet. However, I plan to experiment further.

Debugging

The script uses the debug library. Debugging can be turned on with the -v or --verbose flag or the DEBUG='nothing-major' environment variable.

Related Work

Similar breaking change detection functionality is provided by cracks. cracks checks test files out in the same directory, which can cause lost changes if run on an uncommitted directory. As it hasn't been updated in awhile, I decided to write something fresh.