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

curr-ver

v1.0.7

Published

No nonsense way to write current version details to a file.

Downloads

11

Readme

Curr-Ver

Write current version details in the format of a json object to stdout.

Description

This executable is a no-nonsense way to output current npm version and git hash details, for consumption by other scripts. This is also handy for generating version details to be consumed by a web frontend.

Writes to stdout, and is unopinionated about what to do with the version information.

Note: This assumes you desire to leverage both npm and git version details.

Usage

Run manually from the command line with:

npx curr-ver

Write those details to a file like:

npx curr-ver > ./.version.json

Install as a utility in your project:

npm install --save-dev curr-ver

Run as a commit hook with a utility like Husky. In your package.json:

  "husky": {
    "hooks": {
      "post-commit": "curr-ver > ./.version.json",
      "post-checkout": "curr-ver > ./.version.json"
    }
  }

Below are available cmd line args.

Output sample:

{"version":"1.0.1","hash":"6fb8b2d7"}

Arg | default | description --|--|-- --suffix | none | Adds a suffix to the version, such as 'dev' in 1.0.0-dev --git-dir | none | If operating at a different location than the project root (alongside ./.git). Useful if receiving the error fatal: Not a git repository: '.git'

Roadmap

Things to do (ideas)

  • Add branch information
  • (maybe) add file output option
  • Add other suggested options