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

dl-tgz

v0.7.1

Published

Download and extract a gzipped tar archive with the Observable API

Downloads

71

Readme

dl-tgz

npm version Build Status Build status Coverage Status

A Node.js module to download and extract a gzipped tar archive with the Observable API

const {readdirSync} = require('fs');
const dlTgz = require('dl-tgz');

const url = 'https://****.org/my-archive.tar';
/* my-archive
   ├── LICENSE
   ├── README.md
   ├── INSTALL
   └── bin
       └── app.exe
*/

dlTgz(url, 'my/dir').subscribe({
  next({entry}) {
    if (entry.bytes !== entry.header.size) {
      return;
    }

    console.log(`✓ ${entry.header.name}`);
  },
  complete() {
    readdirSync('my/dir'); //=> ['INSTALL', LICENSE', 'README.md', 'bin']

    console.log('\nCompleted.')
  }
});
✓ bin/
✓ bin/app.exe
✓ README.md
✓ LICENSE
✓ install

Completed.

Installation

Use npm.

npm install dl-tgz

API

const dlTgz = require('dl-tgz');

dlTgz(tarArchiveUrl, extractDir [, options])

tarArchiveUrl: string
extractDir: string (a path where the archive will be extracted)
options: Object
Return: Observable (zenparsing's implementation)

When the Observable is subscribed, it starts to download a tgz archive, extract it and successively send extraction progress to its Observer.

When the Subscription is unsubscribed, it stops downloading and extracting.

Progress

Every progress object have two properties entry and response.

entry

Type: Object {bytes: <number>, header: <Object>}

entry.header is a header of the entry, and entry.bytes is the total size of currently extracted entry. bytes is always 0 if the entry is not a file but directory, link or symlink.

For example you can get the progress of each entry as a percentage by (progress.entry.bytes / progress.entry.header.size || 0) * 100.

dlTgz('https://****.org/my-archive.tgz', 'my/dir')
.filter(progress => progress.entry.header.type === 'file')
.subscribe(progress => {
  console.log(`${(progress.entry.bytes / progress.entry.header.size * 100).toFixed(1)} %`);

  if (progress.entry.bytes === progress.entry.header.size) {
    console.log(`>> OK ${progress.entry.header.name}`);
  }
});
0.0 %
0.1 %
0.3 %
0.4 %
︙
99.6 %
99.8 %
99.9 %
100.0 %
>> OK bin/app.exe
0.0 %
0.1 %
0.2 %
0.3 %
︙
response

Type: Object {bytes: <number>, headers: <Object>, url: <string>}

response.url is the final redirected URL of the request, response.headers is a response header object derived from http.IncomingMessage, and response.bytes is a total content length of the downloaded archive. content-length header will be converted to number if it is string.

Options

You can pass options to Request and tar-fs's extract method. Note that:

License

ISC License © 2017 - 2018 Shinnosuke Watanabe