131 lines
42 KiB
JSON
131 lines
42 KiB
JSON
|
{
|
||
|
"_args": [
|
||
|
[
|
||
|
{
|
||
|
"raw": "tar@^4.0.2",
|
||
|
"scope": null,
|
||
|
"escapedName": "tar",
|
||
|
"name": "tar",
|
||
|
"rawSpec": "^4.0.2",
|
||
|
"spec": ">=4.0.2 <5.0.0",
|
||
|
"type": "range"
|
||
|
},
|
||
|
"/home/jdaugherty/work/GT2/GT2-Android/node_modules/xdl"
|
||
|
]
|
||
|
],
|
||
|
"_from": "tar@>=4.0.2 <5.0.0",
|
||
|
"_id": "tar@4.3.3",
|
||
|
"_inCache": true,
|
||
|
"_location": "/tar",
|
||
|
"_nodeVersion": "8.9.1",
|
||
|
"_npmOperationalInternal": {
|
||
|
"host": "s3://npm-registry-packages",
|
||
|
"tmp": "tmp/tar-4.3.3.tgz_1517948326480_0.17111232038587332"
|
||
|
},
|
||
|
"_npmUser": {
|
||
|
"name": "isaacs",
|
||
|
"email": "i@izs.me"
|
||
|
},
|
||
|
"_npmVersion": "5.6.0-canary.8",
|
||
|
"_phantomChildren": {},
|
||
|
"_requested": {
|
||
|
"raw": "tar@^4.0.2",
|
||
|
"scope": null,
|
||
|
"escapedName": "tar",
|
||
|
"name": "tar",
|
||
|
"rawSpec": "^4.0.2",
|
||
|
"spec": ">=4.0.2 <5.0.0",
|
||
|
"type": "range"
|
||
|
},
|
||
|
"_requiredBy": [
|
||
|
"/xdl"
|
||
|
],
|
||
|
"_resolved": "https://registry.npmjs.org/tar/-/tar-4.3.3.tgz",
|
||
|
"_shasum": "e03823dbde4e8060f606fef7d09f92ce06c1064b",
|
||
|
"_shrinkwrap": null,
|
||
|
"_spec": "tar@^4.0.2",
|
||
|
"_where": "/home/jdaugherty/work/GT2/GT2-Android/node_modules/xdl",
|
||
|
"author": {
|
||
|
"name": "Isaac Z. Schlueter",
|
||
|
"email": "i@izs.me",
|
||
|
"url": "http://blog.izs.me/"
|
||
|
},
|
||
|
"bugs": {
|
||
|
"url": "https://github.com/npm/node-tar/issues"
|
||
|
},
|
||
|
"dependencies": {
|
||
|
"chownr": "^1.0.1",
|
||
|
"fs-minipass": "^1.2.3",
|
||
|
"minipass": "^2.2.1",
|
||
|
"minizlib": "^1.1.0",
|
||
|
"mkdirp": "^0.5.0",
|
||
|
"yallist": "^3.0.2"
|
||
|
},
|
||
|
"description": "tar for node",
|
||
|
"devDependencies": {
|
||
|
"chmodr": "^1.0.2",
|
||
|
"end-of-stream": "^1.4.0",
|
||
|
"events-to-array": "^1.1.2",
|
||
|
"mutate-fs": "^2.1.1",
|
||
|
"rimraf": "^2.6.2",
|
||
|
"tap": "^11.0.0-rc.3",
|
||
|
"tar-fs": "^1.16.0",
|
||
|
"tar-stream": "^1.5.2"
|
||
|
},
|
||
|
"directories": {},
|
||
|
"dist": {
|
||
|
"integrity": "sha512-v9wjbOXloOIeXifMQGkKhPH3H7tjd+8BubFKOTU+64JpFZ3q2zBfsGlnc7KmyRgl8UxVa1SCRiF3F9tqSOgcaQ==",
|
||
|
"shasum": "e03823dbde4e8060f606fef7d09f92ce06c1064b",
|
||
|
"tarball": "https://registry.npmjs.org/tar/-/tar-4.3.3.tgz"
|
||
|
},
|
||
|
"engines": {
|
||
|
"node": ">=4.5"
|
||
|
},
|
||
|
"files": [
|
||
|
"index.js",
|
||
|
"lib/"
|
||
|
],
|
||
|
"gitHead": "9e92533a0724585c695e775d38fc1f64baf8f6ab",
|
||
|
"homepage": "https://github.com/npm/node-tar#readme",
|
||
|
"license": "ISC",
|
||
|
"maintainers": [
|
||
|
{
|
||
|
"name": "othiym23",
|
||
|
"email": "ogd@aoaioxxysz.net"
|
||
|
},
|
||
|
{
|
||
|
"name": "iarna",
|
||
|
"email": "me@re-becca.org"
|
||
|
},
|
||
|
{
|
||
|
"name": "zkat",
|
||
|
"email": "kzm@sykosomatic.org"
|
||
|
},
|
||
|
{
|
||
|
"name": "soldair",
|
||
|
"email": "soldair@gmail.com"
|
||
|
},
|
||
|
{
|
||
|
"name": "isaacs",
|
||
|
"email": "i@izs.me"
|
||
|
}
|
||
|
],
|
||
|
"name": "tar",
|
||
|
"optionalDependencies": {},
|
||
|
"readme": "# node-tar\n\n[![Build Status](https://travis-ci.org/npm/node-tar.svg?branch=master)](https://travis-ci.org/npm/node-tar)\n\n[Fast](./benchmarks) and full-featured Tar for Node.js\n\nThe API is designed to mimic the behavior of `tar(1)` on unix systems.\nIf you are familiar with how tar works, most of this will hopefully be\nstraightforward for you. If not, then hopefully this module can teach\nyou useful unix skills that may come in handy someday :)\n\n## Background\n\nA \"tar file\" or \"tarball\" is an archive of file system entries\n(directories, files, links, etc.) The name comes from \"tape archive\".\nIf you run `man tar` on almost any Unix command line, you'll learn\nquite a bit about what it can do, and its history.\n\nTar has 5 main top-level commands:\n\n* `c` Create an archive\n* `r` Replace entries within an archive\n* `u` Update entries within an archive (ie, replace if they're newer)\n* `t` List out the contents of an archive\n* `x` Extract an archive to disk\n\nThe other flags and options modify how this top level function works.\n\n## High-Level API\n\nThese 5 functions are the high-level API. All of them have a\nsingle-character name (for unix nerds familiar with `tar(1)`) as well\nas a long name (for everyone else).\n\nAll the high-level functions take the following arguments, all three\nof which are optional and may be omitted.\n\n1. `options` - An optional object specifying various options\n2. `paths` - An array of paths to add or extract\n3. `callback` - Called when the command is completed, if async. (If\n sync or no file specified, providing a callback throws a\n `TypeError`.)\n\nIf the command is sync (ie, if `options.sync=true`), then the\ncallback is not allowed, since the action will be completed immediately.\n\nIf a `file` argument is specified, and the command is async, then a\n`Promise` is returned. In this case, if async, a callback may be\nprovided which is called when the command is completed.\n\nIf a `file` option is not specified, then a stream is returned. For\n`create`, this is a readable stream of the generated archive. For\n`list` and `extract` this is a writable stream that an archive should\nbe written into. If a file is not specified, then a callback is not\nallowed, because you're already getting a stream to work with.\n\n`replace` and `update` only work on existing archives, and so require\na `file` argument.\n\nSync commands without a file argument return a stream that acts on its\ninput immediately in the same tick. For readable streams, this means\nthat all of the data is immediately available by calling\n`stream.read()`. For writable streams, it will be acted upon as soon\nas it is provided, but this can be at any time.\n\n### Warnings\n\nSome things cause tar to emit a warning, but should usually not cause\nthe entire operation to fail. There are three ways to handle\nwarnings:\n\n1. **Ignore them** (default) Invalid entries won't be put in the\n archive, and invalid entries won't be unpacked. This is usually\n fine, but can hide failures that you might care about.\n2. **Notice them** Add an `onwarn` function to the options, or listen\n to the `'warn'` event on any tar stream. The function will get\n called as `onwarn(message, data)`. Handle as appropriate.\n3. **Explode them.** Set `strict: true` in the options object, and\n `warn` messages will be emitted as `'error'` events instead. If\n there's no `error` handler, this causes the program to crash. If\n used with a promise-returning/callback-taking method, then it'll\n send the error to the promise/callback.\n\n### Examples\n\nThe API mimics the `tar(1)` command line functionality, with aliases\nfor more human-readable option and function names. The goal is that\nif you know how to use `tar(1)` in Unix, then you know how to use\n`require('tar')` in JavaScript.\n\nTo replicate `tar czf my-tarball.tgz files and folders`, you'd do:\n\n```js\ntar.c(\n {\n gzip: <true|gzip options>,\n file: 'my-tarball.tgz'\n },\n ['some', 'files', 'and', 'folders']\n).then(_ =>
|
||
|
"readmeFilename": "README.md",
|
||
|
"repository": {
|
||
|
"type": "git",
|
||
|
"url": "git+https://github.com/npm/node-tar.git"
|
||
|
},
|
||
|
"scripts": {
|
||
|
"bench": "for i in benchmarks/*/*.js; do echo $i; for j in {1..5}; do node $i || break; done; done",
|
||
|
"genparse": "node scripts/generate-parse-fixtures.js",
|
||
|
"postpublish": "git push origin --all; git push origin --tags",
|
||
|
"postversion": "npm publish",
|
||
|
"preversion": "npm test",
|
||
|
"test": "tap test/*.js --100 -J --coverage-report=text -c"
|
||
|
},
|
||
|
"version": "4.3.3"
|
||
|
}
|