Changelog

The format follows Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

Nothing has been published to npm yet; this becomes 0.1.0 at first release. Until then, "changed" and "fixed" entries refer to the package as used directly from the repository.

Added

• tus 1.0.0 core support as an htmx extension. Add hx-ext="tus" and a data-tus-endpoint, and file inputs upload over tus instead of a normal htmx request.
• Creation, Creation With Upload and Creation Defer Length, via data-tus-endpoint, data-tus-metadata, data-tus-upload-data-during-creation and data-tus-upload-length-deferred.
• Checksum extension — data-tus-checksum hashes every chunk with Web Crypto and sends Upload-Checksum. Supports sha1, sha256, sha384 and sha512. Implemented as an HTTP stack wrapper, exported as createChecksumHttpStack() for wrapping a stack of your own.
• Expiration extension — tus:expires reports the server's deadline, and data-tus-restart-on-expiry starts a fresh upload when the server reports the old one gone. Restarts at most once per file.
• Concatenation across separate files — data-tus-concatenate uploads each file as a partial upload and creates a final upload joining them. data-tus-parallel continues to split a single file across connections.
• Termination — data-tus-terminate on cleanup, plus htmx.tus.terminate(url) and htmx.tus.abort(element, shouldTerminate).
• Capability discovery — data-tus-discover issues the OPTIONS request tus-js-client never makes, reports the result through tus:capabilities, and refuses files larger than the server's Tus-Max-Size.
• Seventeen tus:* events, all bubbling, covering the upload lifecycle, every HTTP request and response, retry decisions, expiry, discovery and concatenation. tus:should-retry is cancelable.
• Auto-resume — data-tus-auto-resume resumes a previous upload of the same file, with tus:resume and tus:auto-resume-error.
• JavaScript API: configure(), resetConfig(), activeUploads, terminate(), abort(), createChecksumHttpStack(), and the tus-js-client module re-exported as tus. Available as ES module exports or on htmx.tus when loaded from a script tag.
• TypeScript declarations, including typed detail payloads for every event through HTMLElementEventMap and DocumentEventMap.
• Documentation at https://sitenetsoft.org/htmx-ext-tus/, generated from the README, with C4 architecture diagrams.

Fixed

• Retries never happened. The onShouldRetry handler returned null when tus:should-retry was not canceled, and tus-js-client uses a handler's return value instead of its own default whenever one is present. No upload ever retried and data-tus-retry-delays had no effect, which defeated the point of a resumable upload client. The default decision is now reproduced faithfully: retry anything that is not a client error, except 409 and 423, while the browser reports itself online.
• Multi-file uploads could hang when one file failed, leaving the completion request unsent.
• data-tus-complete-url was not inherited from ancestor elements.

Changed

• Renamed from htmx-tus to htmx-ext-tus to follow the htmx extension naming convention used by htmx-ext-sse, htmx-ext-ws and others.
• Relicensed from Apache-2.0 to 0BSD, matching htmx and its official extensions.

Known limitations

• Checksum Trailer cannot be supported. No browser exposes an API for sending HTTP request trailers. It is also unnecessary here: every chunk is buffered before being sent, so the digest is always computable in advance for the plain Upload-Checksum header.
• Resuming after a page reload requires the file to be re-selected. tus URL storage persists the upload URL, not the file, and browsers will not reopen a local path without user action.
• Server support for extensions varies. Notably tusd implements neither Checksum nor Expiration; data-tus-discover reports what a server actually offers.