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

upakovka

v0.0.1

Published

The best tool for monorepo

Downloads

3

Readme

upakovka

With upakovka(1) you manage your nodejs monorepo project as a single large npm package.

You have single package.json and relative imports between internal modules - a simple structure which every developer and tool understands.

For deployment or publishing you split your codebase into individual packages.

Usage

Create packing.json file in the project's root directory

{
    "outDir": "packages", // output directory where to build individual packages
    "packages": [
        {
            "name": "tool-1", // name of the target package
            "js": [ // list of js entry points
                "lib/tool-1/main.js"
            ],
            "files": [ // list of non-js files to include into package
                {name: "README.md", src: "docs/tool-1/README.md"},
                "lib/tool-1/config.txt"
                // you don't have to list `.js.map` or `.d.ts` files here, 
                // they will be included automatically
            ],
            "package_json": { // miscellaneous fields to put into `package.json`
                // upakovka(1) will supply defaults for some fields like `.version`, `.author`, `.license`
                // based on the content of the project's `package.json`.
                "description": "tool-1 is for..."
            }
        }
    ]
}

Then just run upakovka with no arguments, and it will generate specified packages.

How it works

For each package it recursively traverses js files by parsing commonjs require calls. It includes each internal module into the target package and for each external dependency it creates an entry in .dependencies of package.json.

Caveats

This is an alpha quality software. Below is a list of issues we hope to fix soon:

  • There is no support for package-lock.json.
  • Supports only commonjs modules and ES2018 version of JavaScript
  • Although .d.ts files corresponding to .js modules will be included automatically, pure .d.ts declarations will be omitted. You have to list those manually under .files.
  • There is no support for code splitting scenarios where you want to put each file into exactly one package.

Installation

via npm

npm install upakovka