fstream-npm causes npm to produce tarballs with missing directory metadata

[sochotnicky]

It seems that due to following approach:

// we don't want empty directories to show up in package
// tarballs.
// don't emit entry events for dirs, but still walk through
// and read them.  This means that we need to proxy up their
// entry events so that those entries won't be missed, since
// .pipe() doesn't do anythign special with "child" events, on
// with "entry" events.

tar files produced with npm are missing directory permission/metadata information completely. This can cause several problems. One of them being that tarballs regenerated from identical sources will have different hashes due to directory creation times being lost. It's possible this could instead be fixed in npm itself by injecting directory entries for all filenames before generating tarballs.