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

tar-edison

v0.1.16

Published

tar for node

Downloads

3

Readme

node-tar

Tar for Node.js.

Goals of this project

  1. Be able to parse and reasonably extract the contents of any tar file created by any program that creates tar files, period.

    At least, this includes every version of:

    • bsdtar
    • gnutar
    • solaris posix tar
    • Joerg Schilling's star ("Schilly tar")
  2. Create tar files that can be extracted by any of the following tar programs:

    • bsdtar/libarchive version 2.6.2
    • gnutar 1.15 and above
    • SunOS Posix tar
    • Joerg Schilling's star ("Schilly tar")
  3. 100% test coverage. Speed is important. Correctness is slightly more important.

  4. Create the kind of tar interface that Node users would want to use.

  5. Satisfy npm's needs for a portable tar implementation with a JavaScript interface.

  6. No excuses. No complaining. No tolerance for failure.

But isn't there already a tar.js?

Yes, there are a few. This one is going to be better, and it will be fanatically maintained, because npm will depend on it.

That's why I need to write it from scratch. Creating and extracting tarballs is such a large part of what npm does, I simply can't have it be a black box any longer.

Didn't you have something already? Where'd it go?

It's in the "old" folder. It's not functional. Don't use it.

It was a useful exploration to learn the issues involved, but like most software of any reasonable complexity, node-tar won't be useful until it's been written at least 3 times.