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-to-json

v2.1.4

Published

A simple Node module for retrieving and writing git commit info to JSON.

Downloads

73

Readme

git-to-json

Read your project's latest git commit info and write it to JSON

Upgrading from v1.X.X to v2.X.X? See the upgrade guide

git-to-json is a simple NPM module designed to retrieve the info for your project's most recent git commit and write it to a file in JSON format as an exportable module.

Installation

NPM

npm install --save git-to-json

Usage

The default behavior of git-to-json is to read the info from your most recent git commit and write it to the file git-commit-info.js, adjacent to your package.json file.

Example of a git-commit-info.js file:

module.exports = {"commit":"5aqfaa6741871zz5e67683a012a0062bdbd46a8z","author":"Foo Bar <[email protected]>","date":"Sun Feb 11 13:37:29 2018 -0500","message":"My cool git commit"}

To run git-to-json, simply include the following command in the NPM script of your choice:

git-to-json

for example, in your project's package.json file:

"scripts": {
  "start": "git-to-json && node index.js"
}

It probably goes without saying, but this app requires that it is run in a directory that has been established as a git repository.

Options

As noted, the default behavior is to create a file named git-commit-info.js adjacent to your package.json file. You can also provide an optional directory and customize the file's name and content with the following options:

--dir <path/to/dir>     specify the relative file path
--name <filename.js>    specify the name of the file
--upcasekeys            set the keys of the exported JSON as uppercase

For example:

git-to-json --dir gitignore --name commit-info

will result in gitignore/commit-info.js.

As of v2.X.X, you can provide a file path of any depth:

git-to-json --dir gitignore/git-info/latest --upcasekeys

will result in gitignore/git-info/latest/git-commit-info.js with uppercased keys - "COMMIT", etc...

If the directory provided does not exist, git-to-json will create it. If it does exist, git-to-json will output the file to the existing directory.

Notes

This module has been formatted according to ESLint's eslint-config-airbnb-base rules.