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

unzippo

v1.0.4

Published

One-liner approach to safely read streams from zip files

Readme

workflow Jest coverage

unzippo is a thin wrapper around node-stream-zip that does all the actual job. The only thing the present module provides is a procedural API for atomic operations.

Atomic here means a zip file is opened, its central directory is read and then the resources are disposed for each separate call. In most cases, this cause no significant overhead but allows to write simpler, cleaner code.

Since the async API is implemented by the original node-stream-zip, there is little sense left to wrap it any more.

Still, one may prefer to use one liners instead of coping with the mandatory asynchronous .close().

Installation

npm install unzippo

Basic usage

const zip = require ('unzippo')

const entries = await zip.list ('/some/archive.zip')

(await zip.open ('/some/archive.zip', 'logs/access.log')).pipe (process.stdout)

const txt   = await zip.read ('/some/archive.zip', 'README.txt')
const wenzi = await zip.read ('/some/archive.zip', 'README.txt.zh', 'ucs2')

const buf   = await zip.get  ('/some/archive.zip', 'images/0.gif')

Listing the archive content

const entries = await zip.list (zipFileName)

returns exactly the same data structure as node-stream-zip's zip.entries():

{
  '/path/to/someEntry': {
    name: '/path/to/someEntry', // same as the key
    size: 354354,               // uncompressed, bytes
    ...,                        // technical info
  },
  ...                           // other entries
}

Extracting a file as a stream

const in = await zip.open (zipFileName, entryPath) // .pipe (myXform)...

returns the binary readable stream corresponding to entryPath inside zipFileName.

This is the preferred, recommended way to read files from zip archives as it causes no memory related risk.

Reading a whole file

For a small file, it may be acceptable to read it at once, in form of Buffer:

const buf = await zip.get (zipFileName, entryPath)

In most cases, such files have text content, so it's handier to have it as a String:

const txt = await zip.read (zipFileName, entryPath) // utf8
const txt = await zip.read (zipFileName, entryPath, encoding)