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

gitpeek

v1.1.2

Published

A fast way to recursively get git information per project on your working station

Downloads

16

Readme

gitpeek

npm

A fast and easy way to recursively show gitlogs per project on your working station.

Install

Globally

npm i -g gitpeek

or

Locally

npm i gitpeek

Usage

Use gitpeek --help for all available commands.

gitpeek --project-path="/Users/you/code" --since="2020-02-17" --author=marnix

const gitpeek = require('gitpeek');
gitpeek({ projectPath: '/Users/user/code', since: '2020-02-17' }).then(data => {
  console.log('data', data);
});

Options

gitpeek in terminal

  --current-user               use the current GIT user as author (default: false)
  --author <author>            pass an author (default: false)
  --day <YYYY-MM-DD>           pass a date of a specific day (default: false)
  --since <YYYY-MM-DD>         pass a start date (default: false)
  --until <YYYY-MM-DD>         pass a until date (default: false)
  --format <format>            formats the git output (default is "%an <%ae> - %s" (default: "%an <%ae> - %s")
  --project-path <path>        pass a project path, which will be used to search for git directories (default: __dirname)
  --skip-directories <string>  pass directory names which should be skipped (default: null)
  --json                       give a json response
gitpeek in node

gitpeek({
  currentUser: false,
  author: false,
  day: false,
  since: false,
  until: false,
  format: '%an <%ae> - %s',
  projectPath: __dirname,
  skipDirectories: null,
  json: true,
}).then(result => console.log('result', result));

Options defaults

author > If not passed, commits of all contributors are listed since > If not passed, today (00:00) is used until > If not passed, the current time is used format > If not passed '%an <%ae> - %s' is used projectPath > If not passed, the current directory is used (__dirname) skipDirectories > already included directories: ['node_modules', 'public', '.git', '_scripts', 'app', 'vendor']

When passing the --skipDirectories argument, make sure to pass it as a string, separating directories with a comma (,). eg. showgitlogs --projectPath="/Users/you/code" --skipDirectories=".next,.cache"

Output formatting

By default, the default formatting outputs author <author email> - commit message (). You can pass your own formatting by passing --format="<format>" to the script. Formatting options can be found here https://git-scm.com/docs/pretty-formats.

Example result

Getting git logs for 17-02-2020 from mjanssen

/Users/marnix/code/projects/some-awesome-project/.git
mjanssen <[email protected]> - Render correct items for language
mjanssen <[email protected]> - Update zindex for social icons

License

MIT