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

gtni

v1.7.0

Published

Install your all npm dependencies recursively with gtni while you are doing git clone, fetch or pull

Downloads

77

Readme

gtni

Install your npm dependencies recursively with gtni as soon you clone, fetch or pull a git repo.

version Downloads Travis branch Greenkeeper badge semantic-release

gtni automatically choose right package manager for a git repository based on lock file in a directory with package.json.

Installation

[sudo] npm install -g gtni
# or
[sudo] yarn global add gtni

Usage

$gtni --help

Usage: gtni <command> [options]

Commands:
  pull   git pull and install npm dependencies
  fetch  git fetch and install npm dependencies
  clone  clone a git repository and install npm dependencies

Options:
  -h, --help     Show help  [boolean]
  -v, --version  Show version number  [boolean]

Examples:
  [NODE_ENV=<env>] gtni pull [git-options]  git pull and install npm packages



# Sub command options

$ gtni <command> -h
Options:
  -h, --help, --help  Show help  [boolean]
  --branch, -b        remote branch name to clone  [string] [default: false]
  --debug, -d         Show debug output  [boolean] [default: false]
  -v, --version       Show version number  [boolean]

  Note: here you can pass any flags for the corresponding git command

I need your help to improve this module. Please send me your valuable suggestions and advices. I am all ears.

Todo List

  • [x] Very basic stage of pull support
  • [x] Pull support for most used git pull options
  • [x] Fetch support for most used git fetch options
  • [x] Support for git clone
  • [x] NODE_ENV support for npm/yarn install
  • [x] Show warnings during dependencies installation
  • [x] Support for read and install dependencies when project has multiple package.json files
  • [x] Install npm modules diffing git tree for various branch after doing git operations supported by gtni
  • [x] Add support to pass custom NODE_ENV values for npm install
  • [x] Choose right package manager automatically for a repository