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

in-version

v0.3.0

Published

Fancy git-tagging for npm modules.

Downloads

2

Readme

in-version

Fancy git-tagging for npm modules.

This project provides a command line utility to create git tags of an npm install-able version of your module.

The npm package manager allows you to install modules directly from a git endpoint. This is great but can lead to larger package installs than necessary. in-version creates tags that include only those files which npm would grab during a publish - usually whatever is listed in the main attribute of your package.json.

Installation

You will typically want to install in-version globally:

npm install --global in-version

For pro points you can install in-version locally:

npm install --save-dev in-version

Usage

Once installed, in-version makes the inv command available to you. This command behaves a lot like npm version.

inv minor

After running the above:

  • The minor version number in your package.json will be incremented (a la npm version)
  • A published-things-only tag will have been created (e.g. v1.1.0)
  • The working copy will have been tagged as the corresponding dev version (e.g. v1.1.0-dev)

If in-version was installed locally you can either invoke it directly from ./node_modules/.bin/inv or create an npm script to run it.

For more information run inv --help or take a look at usage.txt.

License

MIT