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

git-as-npm

v0.0.3

Published

git-as-npm ===

Downloads

4

Readme

git-as-npm

A quick and dirty (for now) script that gets git to behave a little more like NPM at times when we'd like it to. publish is the only command that currently works. Like so:

git-as-npm publish

Why?

NPM is great for managing JS modules. However, private modules aren't free, and maintaining your own registry isn't, either. Thankfully, you can install NPM dependencies directly from Git, like so:

"blah-lib": "git+ssh://[email protected]/blah/blah-lib.git"

You can also install specific tags or commits, by appending # on the end, like so:

git+ssh://[email protected]/blah/blah-lib.git#0.0.3

But the process by which you tag these releases is entirely manual.

Making it not manual

So what does this script do?

  1. Checks out a branch called release (or creates it if it doesn't exist).
  2. Merges your current branch into release.
  3. Pulls down a remote copy of the release branch, to sync up which version numbers have already been released.
  4. Runs npm prepublish, if that script exists.
  5. Creates a tag with your current package.json version number, throwing an error if that release already exists.
  6. Adds a new remote, as specified in the repository field of package.json
  7. Pushes this up to git
  8. Tidies up after itself, deleting the remote and returning you to your original branch.

Ta-da

It doesn't handle everything - you still need to specify the version when doing an npm install and so on, but hopefully it makes things a little easier.