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

@digitalprimates/packing-tape

v0.1.2

Published

Simplified workspace for project dependencies living in multiple git repositories

Downloads

10

Readme

packing-tape

What is packing-tape

Simplified workspace for project dependencies living in multiple git repositories. packing-tape will aggregate the dependencies/ devDependencies for all subprojects and inject them into the workspace package.json file. Once injected packing-tape will install the dependencies, hoisting them to the project level.

Given a workspace with the following structure:

myWorkspace
|
|___ myProjectA
|       |
|       |___ package.json
|
|___ myProjectB
|       |
|       |___ package.json
|
|___ package.json
|
|___ workspace.json

running packing-tape will modify the workspace package.json file to include all subproject dependencies. Once modified packing-tape will install and hoist all dependencies to the workspace level.

myWorkspace
|
|___ node_modules
|       |
|       |___ All dependencies
|
|___ myProjectA
|       |
|       |___ package.json
|
|___ myProjectB
|       |
|       |___ package.json
|
|___ package.json (Modified)
|
|___ workspace.json

In the case where multiple projects contain different but compatible versions of a dependency, packing-tape will resolve the conflict and install version of the dependency that satisfies both projects. If the conflict can not be resolved, packing-tape will throw an error notifying you of the conflict.

Note: When versioning your project, only commit your base package.json config, not the version modified by packing-tape.

Prerequisites

  1. Your workspace dir must contain a workspace.json that maps module name to module dir.
{
    "links": {
        "myProjectA": "myProjectA",
        "myProjectB": "myProjectB"
    }
}
  1. Submodules must contain a npm package.json file.

Usage

  1. install packing-tape as a dev dependency npm i packing-tape --save-dev
  2. Add packing-tape as a script in the main projects package.json.
"scripts": {
    "workspace:install": "packing-tape"
}
  1. Run the packing-tape script defined in the projects package.json npm run workspace:install

Optional Arguments

-[w]orkspace=workspace.json: specifies the path to the workspace's package.json file. By default packing-tape looks for the package in the main workspace dir.

packing-tape -w=configs/workspace.json

-[i]gnore=(comma separated list of modules to skip): In the case that you would like to skip modules listed in workspace.json as links you can use -i to indicate the moudles to skip.

packing-tape -i=myProjectA,myProjectB

-[c] use npm ci instead of npm i': Uses the npm ci command instead of npm i.

packing-tape -c