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

private-module-manager

v0.1.0

Published

Manage private npm modules on github.

Downloads

2

Readme

Why?

Sometimes you want to install modules from private github repos, but you don't want to have to setup your own npm registry. In development you can just install with a git url, but that won't work in a deployment environment if you need to setup deploy keys for each private repo.

What?

This is a module that provides a script that you can run as a postinstall step in the requiring modules' package.json. You can then add a section to your package.json called privateDependencies. When you run npm install, this module will ensure those extra private scripts get cloned and installed. You can provide your own cloning script (as detailed below) where you will want to setup ssh keys etc in your deployment environment, but for development it should just work.

How?

  • Install

    npm install private-module-manager --save
  • Add a postinstall step to your package.json

    "scripts": {
        "postinstall": "private-module-manager install"
    }
    
  • add privateDependencies to your package.json

    "privateDependencies": {
        "my-module": "[email protected]:foo-bar/my-module#ace-branch"
    }
  • You can set the script used to clone the github repo with the PMM_CLONE_SCRIPT environment variable. The script will be called like:

    /path/to/script.sh <reponame> <repo-url> <directory to clone to> <branch/tag/sha to checkout>

    It is the responsibility of your script to clone the module into the directory, and ensure the correct branch/tag is checked out. A basic script is included as a default, but you'll need yourown if you need to monkey around with ssh deploy keys etc.