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

subprojects

v1.0.0

Published

Simple management tool for dependent subprojects in Node.js environment.

Readme

Subprojects

Simple management tool for dependent subprojects in Node.js environment.

Installation

$ npm install subprojects

About

subprojects just makes both the development and deployment easier.

For example, you develop several great Node.js libraries which you plan to use in your applications. Sometimes, you have to add some new functionality in these libraries and use this functionality immediately in your applications during development process. But you do not want to publish this functionality to npm until the development completion.

What to do?

  • You can merge your libraries code into node_modules every time you make changes.

  • Or you can rewrite all require statements in your applications and point them to your local libraries, not to to npm modules. Do not forget to revert the changes before publishing/deployment.

  • Or you can copy all your libraries into your applications and manage the same code in the different places.

  • Or you can just ask the simple and lightweight subprojects library to handle all the staff.

How to use?

1. Put this line in your main module before any require statement
require('subprojects');
2. Create the configuration file for all your local dependencies (name it, for example, "/home/test/subprojects.json" )
{
    "mygreatlib": "/home/test/work/libs/mygreatlib"	
}
3. Setup environment variable NODE_LOCAL_SUBPROJECTS for development
export NODE_LOCAL_SUBPROJECTS=/home/test/subprojects.json
4. require your libraries as if they are in npm
var mygreatlib = require('mygreatlib');
5. Do NOT set the NODE_LOCAL_SUBPROJECTS in production environment to load your libraries from npm

This is it!

Contributors

Author: MileAit

License

Public Domain - Unlicense

All the code is original, written from the scratch to avoid any possible license conflicts.