Tar dependencies are unpacked to wrong directory

[mziech]

This is a follow-up to #23, #24, #25 and #26. While extracting the .tgz dependencies no longer throws an error, the resulting files are probably extracted to the wrong directory. This might be caused by an API change between node-tar 2.x and 3.x where the parameter path of the former Extract method call was changed to cwd of the new x method call.
See: https://www.npmjs.com/package/tar#tarxoptions-filelist-callback-alias-tarextract

While #26 changed the code to use x, the options passed to the method have not been adjusted. This probably leads to the dependencies to be extracted to the current working directory instead of bower_components. In bower_components there will be a directory for the dependency which contains nothing but a .bower.json file.

Please verify and possibly adjust the tar.extract method call to used the cwd option.

[kimtuck]

This caused me much grief over the last couple of days as well. Do you want a PR for this fix?

[mziech]

There is #28, which seems to fix the problem.

[armujahid]

So for now we should use v1.0.2

[joedragons]

FYI, Sonatype only lightly monitors issues here, I have created a parity issue on our JIRA and it's on our team radar. https://issues.sonatype.org/browse/NEXUS-19735

[Deklin]

Hitting the same issue, forcing 1.0.2 seems to work.