https://github.com/meteor/node-tar
tar for node
https://github.com/meteor/node-tar
Last synced: 5 months ago
JSON representation
tar for node
- Host: GitHub
- URL: https://github.com/meteor/node-tar
- Owner: meteor
- License: isc
- Fork: true (isaacs/node-tar)
- Created: 2016-08-12T17:55:38.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2016-08-01T08:08:48.000Z (almost 9 years ago)
- Last Synced: 2024-02-22T01:32:54.293Z (over 1 year ago)
- Language: JavaScript
- Homepage:
- Size: 345 KB
- Stars: 2
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# node-tar
Tar for Node.js.
[](https://nodei.co/npm/tar/)
## API
See `examples/` for usage examples.
### var tar = require('tar')
Returns an object with `.Pack`, `.Extract` and `.Parse` methods.
### tar.Pack([properties])
Returns a through stream. Use
[fstream](https://npmjs.org/package/fstream) to write files into the
pack stream and you will receive tar archive data from the pack
stream.
This only works with directories, it does not work with individual files.
The optional `properties` object are used to set properties in the tar
'Global Extended Header'. If the `fromBase` property is set to true,
the tar will contain files relative to the path passed, and not with
the path included.
### tar.Extract([options])
Returns a through stream. Write tar data to the stream and the files
in the tarball will be extracted onto the filesystem.
`options` can be:
```js
{
path: '/path/to/extract/tar/into',
strip: 0, // how many path segments to strip from the root when extracting
}
```
`options` also get passed to the `fstream.Writer` instance that `tar`
uses internally.
### tar.Parse()
Returns a writable stream. Write tar data to it and it will emit
`entry` events for each entry parsed from the tarball. This is used by
`tar.Extract`.