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 🙏

© 2026 – Pkg Stats / Ryan Hefner

inner-package-manager

v1.1.16

Published

A CLI tool to manage git-tracked inner packages.

Readme

Inner Package Manager

npm Build Status License

Installation

npm i inner-package-manager

Description

The idea behind this project is to provide a way to handle dependencies that will be tracked by git.

How to use

First of all, you will need a file called inner-packages.json in the root of your project. This file will contain the dependencies of your project.

{
  "packages": [
    {
      "name": "your-package-name",
      "repo": "https://github.com/your-github-user/your-repo-name.git",
      "at": "master",
      "targetDir": "your/relative/target/directory"
    }
  ]
}

note: The at field is optional, you can use it to specify a branch, tag or commit hash. note: The targetDir field is optional, you can use it to specify a relative directory where the files will be copied else will be at the repos folder.

To create an inner-packages.json file for you if not exists you can run the following command.

npm inner init

Then run the following command to install the required dependencies.

npm inner install

To install a certain package you can run the following command.

npm inner install your-github-repo-url

Under the hood

The tool will clone the repository at the given branch, tag or commit hash. Then it will copy the files from the cloned repository to the root of your project. But excluding the .git This also will look for a package.json file (if exists) in the root of the cloned repository and will install the dependencies of the cloned repository. As well as the dependencies on an inner-packages.json file in the cloned repository.

Contributing

Contributions are welcome! If you'd like to contribute to this library, please fork the repository and submit a pull request.

How to Contribute Fork the repository.

  • Create a new branch for your feature git checkout -b feature-name
  • Commit your changes git commit -am 'Add new feature'
  • Push to the branch git push origin feature-name
  • Open a pull request. I'll be happy to review it!

License

This project is licensed under the GPL-3.0 License.

Author

Marcos Alvarez