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-project

v0.1.0

Published

The goal of this project is to add features to git for sub projects management.

Downloads

1

Readme

git-project

With git-project, you can manage the projects to checkout even if these are all in the same git repository. It uses the new feature available in git v1.7: sparse-checkout.

It is based on 2 elements:

  • a file format to define your different projects inside the git repository
  • a tool to read the config files and simplify git sparse-checkout commands (git clone is no more efficient)

The goal is not replace git but simplify its management for multi-projects repository.

And for whose who don't think that one git repository for all project is good practise: google did it so why not someon else.

Install

# as a node module
npm install gitp

# as a cli
npm install -g gitp

Getting started

In order to use git-project, follow these steps:

On your repository:

  1. create a .gitprc config file in the repository you can to checkout
  2. define your project in the .gitprc file (see example)

As a CLI

Where you want to checkout only a sub part of the repository:

  1. npm install -g git-project to install git-project on your computer
  2. use command gitp init [<ref>] <url> to define the repository to pull
  3. use command gitp config project <project1> <project2> to define the projects to pull
  4. use command gitp pull <ref> <branch> and it will automatically pull what you want

Onyl this 3 commands exists, use standard git commands for other operations.

As a node module

var gitp = require('git-project')(<dirname>);

gitp.init(<url>, [<ref>,] callback);
gipt.configureProjects([<project1>, <project2>, ..], callback);
gitp.pull(<ref>, <branch>, callback);