Tar React Native Reference Documentation

Tar

Current Version: 11.6.1

Chilkat.Tar

Create, list, verify, filter, and extract TAR archives and compressed TAR formats.

Chilkat.Tar creates, verifies, lists, and extracts TAR archives, including compressed TAR formats such as .tar.gz, .tgz, .tar.bz2, and .tar.Z. It supports adding individual files and directory trees, controlling archive paths, preserving or overriding file permissions, filtering included or extracted files, extracting from memory, extracting selected entries to memory or BinData, producing XML listings, and creating Debian .deb package archives from control and data tarballs.

Create TAR archives

Add files or directory trees and write standard TAR output, with control over archive paths, directory handling, and write format.

Compressed TAR formats

Work with common compressed archive forms such as .tar.gz, .tgz, .tar.bz2, and .tar.Z.

List and verify contents

Inspect archive entries, verify archive structure, and produce XML listings for display, logging, or programmatic processing.

Selective extraction

Extract entire archives or selected entries, including workflows that extract matching files directly to memory or BinData.

Filters and paths

Include or exclude files using filters, control relative paths in the archive, and manage how entries are restored during extraction.

Permissions and packages

Preserve or override UNIX-style permissions and create Debian .deb package archives from control and data tarballs.

Common pattern: Use Tar when the data is a TAR archive or a compressed TAR archive. Configure the archive paths, filters, permissions, and compression format, then create, list, verify, or extract the archive as needed. Use Chilkat.Zip for ZIP archives, Chilkat.Gzip for a single GZIP stream, and Chilkat.Compression for raw compression operations.

Object Creation

// npm install @chilkat/react-native react-native-nitro-modules
// (React Native 0.76+ with the New Architecture; then `pod install` for iOS.  The Chilkat
//  native library is downloaded and verified during the native build -- see the package README.)

import { Chilkat, Tar } from '@chilkat/react-native'

// Once per app start, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial')   // shorthand for new Global().unlockBundle(..)

const tar = new Tar()
// ... the native object is released when `tar` is garbage collected, or now with tar.dispose()
new Tar()

Creates the underlying native Chilkat object. Tar is a Nitro Module HybridObject: use it from the JavaScript thread only (it cannot be passed to a Worklet or another runtime). Every member is synchronous and blocks the JavaScript thread until Chilkat returns; a method that can take a while also exists as a ...Async twin returning a Promise, which runs the same call on a native worker thread so the UI keeps rendering. While such a call is pending, every other call on this object throws, except abort() and assigning onPercentDone / onProgressInfo.

dispose(): void

Releases the native object immediately instead of waiting for garbage collection (useful for a large BinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws. An object with a pending ...Async call cannot be disposed until the promise settles.

Errors

A method that can fail throws a plain Error: a method whose only outcome is success or failure returns void and throws on failure; a method producing a string or an object returns it and throws where Chilkat would have returned null. The error's message is "Class.method(...): reason", where the reason is the last informative line of the object's lastErrorText, which holds the full Chilkat log of the failed call. A ...Async twin rejects its promise with the same Error instead of throwing. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain boolean.

try {
  tar.someMethod(...)
} catch (e) {
  console.log((e as Error).message)   // Tar.someMethod(...): <reason>
  console.log(tar.lastErrorText)   // the full Chilkat log of the failed call
}

// The same call without blocking the JavaScript thread:
try {
  await tar.someMethodAsync(...)
} catch (e) {
  console.log((e as Error).message)   // Tar.someMethodAsync: <reason>
}

Properties

CaptureXmlListing
// read/write
captureXmlListing: boolean
Introduced in version 9.5.0.46

Controls whether extraction methods also capture an XML inventory of the archive. When set to true, methods such as Untar, UntarGz, UntarBz2, and UntarZ store the listing in XmlListing. The XML has the same structure as the string returned by ListXml. The default is false.

Inspect without extracting: Set CaptureXmlListing and SuppressOutput to true before an untar operation to scan the archive and obtain its XML listing without writing archive entries to disk.

top
Charset
// read/write
charset: string

Specifies the character encoding used to decode filenames stored in a TAR archive during extraction. The default is utf-8, which is normally appropriate for modern archives.

This property affects archive entry names only. It does not convert or otherwise alter the contents of extracted files. TAR archives written by the WriteTar* methods store filenames as UTF-8.

Filename interoperability: The original TAR header format does not always identify the character encoding of a filename. Change this property only when an older archive is known to use a different encoding.

top
DebugLogFilePath
// read/write
debugLogFilePath: string

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
DirMode
// read/write
dirMode: number

Specifies the UNIX permission bits written to the TAR header for directory entries created by the WriteTar* methods. The default is octal 0755, which represents rwxr-xr-x.

Archive metadata: This value records permissions in the archive. Whether the exact permissions are restored during extraction depends on the destination operating system, filesystem, process privileges, and local security policy.

top
DirPrefix
// read/write
dirPrefix: string

Specifies a path prefix to prepend to entries when a TAR archive is created. For example, setting this property to subdir1 causes an entry such as report.txt to be stored as subdir1/report.txt.

The prefix changes only the path stored in the archive; it does not rename or move the source file on disk.

AddFile2 exception: AddFile2 explicitly supplies the complete path within the archive, so DirPrefix is not applied to files added by that method.

top
FileMode
// read/write
fileMode: number

Specifies the UNIX permission bits written to the TAR header for ordinary file entries created by the WriteTar* methods. The default is octal 0644, which represents rw-r--r--.

Shell scripts: Files recognized as shell scripts use ScriptFileMode instead, allowing executable permissions to be recorded separately.

top
GroupId
// read/write
groupId: number

Specifies the numeric group identifier (GID) written to TAR headers when an archive is created. The default value is 1000.

Ownership metadata: A stored GID is archive metadata. Restoring ownership may require elevated privileges and may be ignored or mapped differently on non-UNIX systems.

top
GroupName
// read/write
groupName: string

Specifies the group name written to TAR headers when an archive is created. By default, Chilkat uses the username of the account running the application.

Name versus numeric ID: TAR headers can contain both a group name and the numeric GroupId. Extraction tools and operating systems may give different precedence to these fields.

top
HeartbeatMs
// read/write
heartbeatMs: number

Specifies the approximate interval, in milliseconds, between AbortCheck event callbacks during supported long-running operations. The default is 0, which disables periodic AbortCheck callbacks.

Cancellation is cooperative: A callback can request that an operation stop, but the request is observed only when the running method reaches a cancellation check. Short operations may finish before a callback occurs.

More Information and Examples
top
LastErrorHtml
// read-only
readonly lastErrorHtml: string

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
// read-only
readonly lastErrorText: string

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
// read-only
readonly lastErrorXml: string

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
// read/write
lastMethodSuccess: boolean

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
MatchCaseSensitive
// read/write
matchCaseSensitive: boolean
Introduced in version 9.5.0.46

Controls whether the patterns in MustMatch and MustNotMatch are matched case-sensitively. The default is false.

Cross-platform behavior: Case sensitivity in the archive filter is independent of whether the local filesystem itself treats filenames as case-sensitive.

top
MustMatch
// read/write
mustMatch: string
Introduced in version 9.5.0.46

Specifies an inclusion pattern applied when creating or extracting TAR archives, including compressed TAR formats. A candidate path is included or extracted only when it matches this pattern. The default is an empty string, which permits all paths.

The pattern may contain zero or more asterisks (*), where each asterisk matches zero or more characters. For example, *.txt selects paths ending in .txt. Case handling is controlled by MatchCaseSensitive.

Combined filters: If both MustMatch and MustNotMatch are set, a path must satisfy the inclusion pattern and must not satisfy the exclusion pattern.

top
MustNotMatch
// read/write
mustNotMatch: string
Introduced in version 9.5.0.46

Specifies an exclusion pattern applied when creating or extracting TAR archives, including compressed TAR formats. A candidate path that matches this pattern is skipped. The default is an empty string, which excludes nothing.

The pattern may contain zero or more asterisks (*), where each asterisk matches zero or more characters. For example, *.obj skips paths ending in .obj. Case handling is controlled by MatchCaseSensitive.

Exclusion takes effect after inclusion: When both filters are set, matching MustMatch does not override a match in MustNotMatch.

top
NoAbsolutePaths
// read/write
noAbsolutePaths: boolean

Controls whether absolute archive paths are converted to relative paths during extraction. When true, a leading / or \ is removed before the entry is written. The default is true.

Recommended security setting: Keep this property enabled when extracting archives you did not create. Also extract untrusted archives into a dedicated directory and inspect their entry names before relying on the extracted content.

top
NumDirRoots
// read-only
readonly numDirRoots: number

Returns the number of directory roots currently registered for archive creation by calls to AddDirRoot and AddDirRoot2. Individual files added with AddFile or AddFile2 are not included in this count.

Use zero-based indexes from 0 through NumDirRoots - 1 with GetDirRoot.

top
PercentDoneScale
// read/write
percentDoneScale: number
Introduced in version 9.5.0.49

Specifies the value reported by PercentDone when an eligible operation is 100% complete. The default is 100. Increasing the scale allows finer-grained integer progress values; for example, a scale of 1000 allows 453 to represent 45.3%.

The value is clamped to the range 10 through 100000. This property is available only in environments that support event callbacks, and only methods for which measurable progress is available emit percentage updates.

Scale, not frequency: A larger scale increases the numeric resolution of progress values but does not guarantee a callback for every possible value.

top
ScriptFileMode
// read/write
scriptFileMode: number

Specifies the UNIX permission bits written to TAR headers for shell-script files recognized by extensions such as .sh, .csh, .bash, and .bsh. The default is octal 0755, which records executable permissions.

Other files: Non-script files use FileMode; directories use DirMode.

top
SuppressOutput
// read/write
suppressOutput: boolean
Introduced in version 9.5.0.46

Controls whether untar operations write extracted files and directories to the filesystem. When true, methods such as Untar, UntarGz, UntarBz2, and UntarZ scan the archive without producing extracted output. The default is false.

Archive inventory workflow: Combine this property with CaptureXmlListing to obtain an XML listing without extracting the archive.

top
UntarCaseSensitive
// read/write
untarCaseSensitive: boolean

Deprecated. Use MatchCaseSensitive instead.

Until this property is removed, reading or setting it has the same effect as reading or setting MatchCaseSensitive.

top
UntarDebugLog
// read/write
untarDebugLog: boolean

Controls whether untar methods add per-entry extraction details to LastErrorText, LastErrorXml, and LastErrorHtml. The default is false.

Diagnostic output is not necessarily an error: When this property is enabled, the LastError properties can contain useful extraction trace information even after a successful operation.

top
UntarDiscardPaths
// read/write
untarDiscardPaths: boolean

Controls whether directory components from archive entry names are discarded during extraction. When true, each file is written directly into UntarFromDir rather than recreating the archived directory tree. The default is false.

Filename collisions: Different archive entries can have the same final filename after their directory paths are removed. Use this option only when flattening the archive is intentional and potential collisions are acceptable.

top
UntarFromDir
// read/write
untarFromDir: string

Specifies the destination directory for extraction. The default is ., meaning the current working directory of the calling process.

When UntarDiscardPaths is false, archived subdirectories are recreated beneath this directory. When it is true, extracted files are placed directly in this directory.

Safer extraction: For untrusted archives, choose a new or otherwise isolated destination directory rather than extracting directly into an application or system directory.

top
UntarMaxCount
// read/write
untarMaxCount: number

Limits the number of matching entries extracted by an untar operation. The default is 0, which means no maximum.

For example, set MustMatch to select a particular path and set UntarMaxCount to 1 to stop after the first matching entry is extracted.

Archive order matters: When a limit is used, extraction stops after the configured number of matches in archive order.

top
UserId
// read/write
userId: number

Specifies the numeric user identifier (UID) written to TAR headers when an archive is created. The default value is 1000.

Ownership metadata: A stored UID does not by itself change the owner of a local source file. Restoring ownership during extraction may require elevated privileges and may not apply on non-UNIX systems.

top
UserName
// read/write
userName: string

Specifies the user name written to TAR headers when an archive is created. By default, Chilkat uses the username of the account running the application.

Name versus numeric ID: TAR headers can contain both a user name and the numeric UserId. Their interpretation depends on the extracting tool and destination system.

top
VerboseLogging
// read/write
verboseLogging: boolean

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
// read-only
readonly version: string

Version of the component/library, such as "10.1.0"

More Information and Examples
top
WriteFormat
// read/write
writeFormat: string

Specifies the TAR header format used by the WriteTar* methods. The default is gnu. Supported values are:

ValueUse
gnuGNU TAR format and extensions. This is the Chilkat default and supports archive metadata beyond classic ustar limits.
paxPOSIX pax extended format. It is designed to represent long names and additional metadata through extensible records.
ustarPOSIX ustar format. It is broadly interoperable but has stricter limits on path lengths and metadata fields.
Choosing a format: Use ustar when compatibility with simple TAR readers is the priority and the archive fits its limits. Use pax for portable extended metadata, or retain gnu when GNU TAR compatibility is expected.

top
XmlListing
// read/write
xmlListing: string
Introduced in version 9.5.0.46

Contains the XML listing captured by the most recent untar operation for which CaptureXmlListing was true. The XML structure is the same as the output from ListXml.

Read after the operation: Use the untar method's return value to confirm that the archive was processed successfully before consuming this property.

top

Methods

AddDirRoot
addDirRoot(dirPath: string): void

Adds the directory tree at dirPath to the set of sources used by the next WriteTar* operation. Call this method multiple times to include multiple directory trees in one archive.

Use AddDirRoot2 when the tree should appear beneath an explicit prefix inside the archive.

Queued archive sources: Directory roots and files are retained by the object until ClearDirRootsAndFiles is called.

Returns normally on success; throws an Error on failure.

top
AddDirRoot2
addDirRoot2(rootPrefix: string, rootPath: string): void
Introduced in version 9.5.0.56

Adds the directory tree at rootPath to the archive-creation source list and stores its entries beneath the archive prefix supplied in rootPrefix. Call this method multiple times, or combine it with AddDirRoot, before calling a WriteTar* method.

rootPrefix should be a relative archive path such as abc/123 and should not end with /. If DirPrefix is also set, DirPrefix is applied first.

Path composition example: With DirPrefix = "package" and rootPrefix = "assets", files from this root are stored beneath package/assets/.

Returns normally on success; throws an Error on failure.

top
AddFile
addFile(path: string): void
Introduced in version 9.5.0.46

Adds the local file at path to the set of sources used by the next WriteTar* operation. Call AddFile, AddFile2, and the directory-root methods as needed before writing a single archive.

Use AddFile2 when the path stored inside the TAR must be specified independently of the source file path.

Queued archive sources: Added files and directory roots remain associated with the object until ClearDirRootsAndFiles is called.

Returns normally on success; throws an Error on failure.

top
AddFile2
addFile2(filePath: string, pathWithinTar: string): void
Introduced in version 9.5.0.69

Adds the local file at filePath to the archive-creation source list and stores it using the exact archive path supplied in pathWithinTar. This allows the source path and the path visible inside the TAR to differ.

Call this method as many times as needed, optionally together with the other file and directory-root methods, before calling a single WriteTar* method.

DirPrefix is not applied: Because pathWithinTar already specifies the path within the TAR, DirPrefix does not modify entries added by this method. Use forward slashes and a relative path for portable archive names.

Returns normally on success; throws an Error on failure.

top
ClearDirRootsAndFiles
clearDirRootsAndFiles(): void
Introduced in version 9.5.0.84

Removes all files and directory roots previously registered by AddDirRoot, AddDirRoot2, AddFile, and AddFile2.

Call this method before building a different archive with the same Tar object when the earlier source list should not be reused.

Returns normally on success; throws an Error on failure.

top
CreateDeb
createDeb(controlPath: string, dataPath: string, debPath: string): void
Introduced in version 9.5.0.66

Creates a Debian binary package at debPath from the prepared control archive at controlPath and data archive at dataPath. The inputs are typically named control.tar.gz and data.tar.gz, or use another compression form accepted by the target Debian tooling.

Debian package structure: A modern .deb file is an ar archive containing a debian-binary format marker, a control.tar.* member for package metadata and maintainer scripts, and a data.tar.* member for the installed filesystem payload.
Prepared inputs required: This method packages the supplied control and data tarballs. The caller is responsible for making their directory layout, control metadata, permissions, and package contents valid for Debian package-management tools.

Returns normally on success; throws an Error on failure.

top
GetDirRoot
getDirRoot(index: number): string

Returns a directory root previously added with AddDirRoot or AddDirRoot2. index is a zero-based index.

Valid indexes range from 0 through NumDirRoots - 1. For example, after two roots are added, GetDirRoot(0) returns the first and GetDirRoot(1) returns the second.

Throws an Error on failure (where the description says null is returned, the method throws instead).

top
ListXml
listXml(tarPath: string): string

Scans the uncompressed TAR archive at tarPath and returns an XML description of its files, directories, and archive metadata. The archive is not extracted.

Compressed tarballs: For a compressed TAR archive, an untar method can capture the same listing format by setting CaptureXmlListing. Set SuppressOutput as well when no files should be written.

Throws an Error on failure (where the description says null is returned, the method throws instead).

top
ListXmlAsync
listXmlAsync(tarPath: string): Promise<string>

Asynchronous form of ListXml: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
Untar
untar(tarPath: string): number

Extracts the uncompressed TAR archive at tarPath into the directory specified by UntarFromDir. Archived directory trees are recreated unless UntarDiscardPaths is true.

Returns the number of files and directories extracted, or -1 if the operation fails. Extraction is also affected by the matching, path-safety, count-limit, listing, and output-suppression properties of this object.

TAR is a container format: An ordinary .tar archive is not compressed. Use UntarGz, UntarBz2, or UntarZ for the corresponding compressed tarball formats.
More Information and Examples
top
UntarAsync
untarAsync(tarPath: string): Promise<number>

Asynchronous form of Untar: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
UntarBz2
untarBz2(tarPath: string): void

Decompresses and extracts the .tar.bz2 archive at tarPath into UntarFromDir. This format is also commonly named .tbz, .tbz2, or .tb2.

Returns true on success and false on failure. The same extraction filters, path controls, listing options, and output settings used by Untar also apply.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
UntarBz2Async
untarBz2Async(tarPath: string): Promise<void>

Asynchronous form of UntarBz2: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
UntarFirstMatchingToBd
untarFirstMatchingToBd(tarPath: string, matchPattern: string, bd: BinData): void
Introduced in version 9.5.0.82

Scans the uncompressed TAR archive at tarPath and copies the contents of the first file whose archive path matches matchPattern into the BinData object supplied in bd. Matching is evaluated in archive order.

No archive entry is written to the local filesystem. Returns true when a matching file is successfully extracted to bd and false otherwise.

Returns normally on success; throws an Error on failure.

top
UntarGz
untarGz(tarPath: string): void

Decompresses and extracts the .tar.gz archive at tarPath into UntarFromDir. The .tgz extension is a common short form for the same gzip-compressed TAR structure.

Returns true on success and false on failure. The same extraction filters, path controls, listing options, and output settings used by Untar also apply.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
UntarGzAsync
untarGzAsync(tarPath: string): Promise<void>

Asynchronous form of UntarGz: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
UntarZ
untarZ(tarPath: string): void

Decompresses and extracts the .tar.Z archive at tarPath into UntarFromDir. The .Z suffix denotes the historical UNIX compress format; .taz is a common alternate extension.

Returns true on success and false on failure. The same extraction filters, path controls, listing options, and output settings used by Untar also apply.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
UntarZAsync
untarZAsync(tarPath: string): Promise<void>

Asynchronous form of UntarZ: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
VerifyTar
verifyTar(tarPath: string): boolean

Opens the uncompressed TAR archive at tarPath and scans its headers through the end of the archive. Returns true when the archive structure is accepted and no TAR-format errors are found; otherwise returns false.

What verification does not establish: Structural verification does not prove that archived files are safe, trustworthy, or appropriate to extract. It is not malware scanning and does not authenticate the archive publisher.
top
VerifyTarAsync
verifyTarAsync(tarPath: string): Promise<boolean>

Asynchronous form of VerifyTar: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
WriteTar
writeTar(tarPath: string): void

Creates an uncompressed TAR archive at tarPath from the files and directory trees previously added with AddFile, AddFile2, AddDirRoot, and AddDirRoot2. Archive paths, permissions, ownership metadata, filters, and header format are controlled by the corresponding properties.

Returns true on success and false on failure.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
WriteTarAsync
writeTarAsync(tarPath: string): Promise<void>

Asynchronous form of WriteTar: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
WriteTarBz2
writeTarBz2(bz2Path: string): void

Creates a bzip2-compressed TAR archive at bz2Path from the files and directory trees previously added to this object. Common filename extensions include .tar.bz2, .tbz, .tbz2, and .tb2.

Returns true on success and false on failure.

Two-layer format: The result is a TAR byte stream compressed with bzip2. TAR supplies the multi-file archive structure; bzip2 supplies compression.

Returns normally on success; throws an Error on failure.

top
WriteTarBz2Async
writeTarBz2Async(bz2Path: string): Promise<void>

Asynchronous form of WriteTarBz2: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top
WriteTarGz
writeTarGz(gzPath: string): void

Creates a gzip-compressed TAR archive at gzPath from the files and directory trees previously added to this object. The usual extensions are .tar.gz and .tgz.

Returns true on success and false on failure.

Two-layer format: The result is a TAR byte stream compressed with gzip. TAR supplies the multi-file archive structure; gzip supplies compression.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
WriteTarGzAsync
writeTarGzAsync(gzPath: string): Promise<void>

Asynchronous form of WriteTarGz: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.

Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.

Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.

top

Events

While a method runs, Tar reports progress through two optional callback properties. Assign a function to receive the event, or undefined to stop receiving it. The callbacks are delivered on the JavaScript thread, so they are useful with the ...Async methods: during a synchronous call the JavaScript thread is busy inside Chilkat, and the events can only arrive after it returns.

const tar = new Tar()
tar.onPercentDone = (pct) => setProgress(pct)          // pct is 0..100
tar.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
tar.heartbeatMs = 250   // let abort() take effect within a quarter second

const pending = tar.someMethodAsync(...)
cancelButton.onPress = () => tar.abort()   // the promise then rejects
await pending

PercentDone fires when an operation's completion percentage is known; ProgressInfo delivers named progress values (what is reported depends on the class and method). There is no AbortCheck callback: to cancel a pending ...Async call, call abort() on the object. Chilkat notices the request at its next progress check, which happens at least every heartbeatMs milliseconds on the classes that have that property (0, the default, disables the heartbeat, so set it for a responsive cancel), and the promise rejects with Chilkat's abort error. abort() is harmless when nothing is pending.

PercentDone
// callback property; assign undefined to remove
onPercentDone?: (pctDone: number) => void

This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).

The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.

To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.

More Information and Examples

Example:

tar.onPercentDone = (pct) => {
  // pct ranges from 0 to 100.
  setProgress(pct)   // runs on the JavaScript thread: React state may be updated directly
}
await tar.someMethodAsync(...)
// To stop an operation from within the callback, call tar.abort()
top
ProgressInfo
// callback property; assign undefined to remove
onProgressInfo?: (name: string, value: string) => void

This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.

Note: Some Chilkat methods don't fire any ProgressInfo events.

More Information and Examples

Example:

tar.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
await tar.someMethodAsync(...)
top