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 🙏

© 2025 – Pkg Stats / Ryan Hefner

onecommit

v0.0.12

Published

A cli tool to create new branches with just one commit

Readme

OneCommit

A cli tool to create new branches with just one commit

Sometimes you can neither create well organized branches nor rebase your code appropriately.

For example, let's say that you have an error in production that is not replicable otherwhere. Most likely, you will create a lot of commits that you have to push in order to pull the changes where you are debugging your code.

When you finally discover the issue, you have probably done many changes but you have a bad history of commits that don't make sense. How to you clean your code?

OneCommit

  1. compares the differences between your current branch with master (or a different branch)
  2. saves the changes in a working folder
  3. checkouts master
  4. copies back the files in the repo
  5. if you specify one, checkouts -b a new branch

At this point, you can commit with a clear message and create a clean pull request with just one commit.

Install

Use npm (or yarn):

npm i -g onecommit

Usage

Move to the root of the repo and run onecommit. Optionally, you can specify the master branch (if not master) and the new branch to be created with the changes (if you don't do, it will remain in the master branch).

Examples

Use master and stay in master after the restore:

onecommit

Use develop and create the new branch version2 after the restore:

onecommit -d develop -n version2

Commits the current changes before proceeding if not committed yet:

onecommit -c

In general, execute onecommit -h to get an help.

Updates

To update onecommit just run

onecommit -u

Next steps (maybe)

  • Refactoring it to make it easily expandeable.
  • Adding a test unit.

Licence

MIT

Copyright

2019, Francesco Sullo

Enjoy and let me know what do you think :o)