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

ah-packager

v0.2.6

Published

Package content

Downloads

2

Readme

Anthill Packager

Package content as zip.

It's the content of the supplied folders that will be packaged, not the folder itself.

API

var packager = require('ah-packager');
packager(folders, config, callback);

param - folders

The folders to package.

They can be an array of simple strings, an array of full paths, or a string (single folder).

Full paths need to end in a glob pattern, i.e. /**/*

Examples

var packager = require('ah-packager');

packager(['pageOne', 'pageTwo'], {}, function(err, dest) {});
// "dest" ~= packages/projectName-package-2017-05-14T11-01-21
// Zip files will be pageOne.zip and pageTwo.zip

packager(['User/demo/pageOne/build/**/*', 'User/demo/pageTwo/build/**/*'], {}, function(err, dest) {});
// "dest" ~= packages/projectName-package-2017-05-14T11-01-21
// Zip files will be pageOne.zip and pageTwo.zip

packager('pageOne', {}, function(err, dest) {});
// "dest" ~= packages/projectName-package-2017-05-14T11-01-21
// Zip file will be pageOne.zip

packager('dist', {}, function(err, dest) {});
// "dest" ~= packages/projectName-package-2017-05-14T11-01-21
// Zip file will be projectName.zip

config

path

Where to start from. Defaults to '.' (current folder)

output

Where to put the result, relative to current folder. Defaults to './packages'

dest

Name of folder to put the packages in. Defaults to [projectName]-package-[timestamp]

shared

If a folder should be excluded because it's shared across packages, e.g. "node_modules/shared-content" -> "../shared"

Dist folders

Distribution folders get special treatment. If a folder is named "dist" or full paths are used, the generated zip will be named after the parent folder.

Examples

"efficacy-slide/dist" as folders param will generate "efficacy-slide.zip" file in packages folder (default).

["efficacy-slide/build/**/*", "safety-slide/build/**/*"] as folders param will generate "efficacy-slide.zip" and "safety-slide.zip" files in packages folder (default).