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

odb

v0.0.3

Published

Open the dirty files in a branch in a text editor, carry on hackin.

Downloads

9

Readme

~~open-dirty~~ ~~dirtydirty~~ odb

Opening dirty files from a branch.


WIP NOT READY FOR GENERAL USE YET

| :microphone: | :computer: | | --- | --- | | odb | I want to checkout the branch I'm working on then open all the files I've been working on, in that branch, in my text editor. I don't want to fuzzy find them or search through the tree for them or open them once and leave the window open until the PR is merged... No, no. |

What ODB does

It runs git diff --name-only origin/master... the same as you could do on the command line. This gets a list of the files that include changes not on master. ODB then creates another command for opening the text editor with each of those files. It then runs that command.

How to Use

You'll need to have installed Node.js to run ODB and of course Git.

Install

$ npm install -g odb

Use

The default editor is Sublime. You can change it Atom:

$ od --editor atom

Do the same to set it back to Sublime, but type 'subl' (instead of the full name). I can't say how it will work with other editors...

To use, after you cd into the directory for the repo you're working on, run ODB:

$ cd <RepoDirectory>
$ od

The dirty files will open in your text editor :)

It uses the default branch to compare to as master. To change the branch:

$ od gh
# short for gh-pages
$ od <fullbranchname>
# for other branches