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

@aeppic/pack

v1.2.0

Published

Tool for packaging Node.js modules for distribution including all production dependencies.

Downloads

2

Readme

aeppic Packaging Tool

Tool to package a node package including its production dependencies as a binary.

Usage

Run the pack command in the package root (where pnpm-lock.yaml or package-lock reside)

npx @aeppic/pack

or install it globally

npm i -g @aeppic/pack
aeppic-pack

Help for options is available via --help and use -v to see what Docker is doing during the build.

Requirements

Local Docker is required and it needs to support DOCKER_BUILDKIT=1 to passthrough SSH and NPM credentials into the Docker container. Docker version 20.10.11, build dea9396 was used during development.

Two Dockerfiles are included. One for pnpm (Default) and one using npm, but that can be overwritten from the command line. By default an ubuntu:16.04 image is used as a builder image (FROM ubuntu:16.04 as builder)

Way it works

  1. Gather all production files via npm pack using its JSON output
  2. Create a Docker image copy the pnpm/npm lock and run a production level as part of the build
  3. Copy the resulting node_modules folder from inside the container back into the host
  4. Create a new tgz containing the files from step 1 and the node_modules from step 2/3

Important: Make sure the package.json files field includes all files required for runtime

Publishing

Publish this package with --access=public. For some reason npm doesn't use the public: true marker in the package.json and an explicit option is needed for publishing to a scope.