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

npm-pack-all

v1.12.7

Published

A simple utility to package all node_modules dependencies when running `npm pack` (not devDependencies)

Downloads

4,907

Readme

npm-pack-all

Version Build Status Coverage Status code style: prettier js-standard-style

A simple utility to package all node_modules dependencies when running npm pack (not devDependencies)

This can be useful when wanting to ship dependencies as part of the artifact. While one can install dependencies on a deployed target using package-lock.json and yarn.lock, there can be downsides to that approach, as well.

npm-pack-all utility does the following:

  1. Backs up the following files

    • package.json
    • package-lock.json
    • yarn.lock
    • .npmignore
  2. Adds all dependencies as bundledDependencies in the active package.json

    • Pass the --dev-deps flag to add devDependencies along with production dependencies
  3. Generates an empty .npmignore file in the project root

    • If no .npmignore exists, npm pack will use .gitignore to exclude modules

      (node_modules by default in many cases)

  4. Calls npm -dd pack

    • The following will be packed into a .tgz archive:

      • Any files (via glob) called out in the package.json files field
      • All production dependencies (and their dependencies)
      • If --dev-deps, all devDependencies (and their dependencies)
  5. Restores the files that were backed up

Install

npm install npm-pack-all

OR

yarn add npm-pack-all

Use

node node_modules/.bin/npm-pack-all <optional options>

Basic

node node_modules/.bin/npm-pack-all

Options

--output

Output your .tgz artifact to a different directory (or with a different name)

node node_modules/.bin/npm-pack-all --output build/

OR

node node_modules/.bin/npm-pack-all --output build/artifact.tgz

--dev-deps

Bundle all production dependencies AND devDependencies in the artifact (use with care -- your artifact will balloon)

node node_modules/.bin/npm-pack-all --dev-deps --output build/artifact.tgz