@rpldy/tus-sender v1.8.0

TUS Sender

An Uploady sender implementation of the TUS protocol.

Supports version 1.0.0 of the TUS protocol

Under the hood, the tus-sender uses the @rpldy/chunked-sender to upload the files as chunks

The best place to get started is at our: React-Uploady Documentation Website

Installation

#Yarn:
  $ yarn add @rpldy/tus-sender

#NPM:
  $ npm i @rpldy/tus-sender

TUS Protocol

On top of the Core Protocol, Uploady supports the following extensions:

• Creation (creation)
• Creation with Upload (creation-with-upload)
• Concatenation (concatenation)
• Creation Defer Length (creation-defer-length)

It also supports the Upload-Metadata header and will turn the destination/upload options params prop into the metadata key/value.

Options

All of the chunked-sender options are supported with this sender

When the chunked-sender parallel param is set to > 1, the Concatenation tus extension will be used. It will send the chunks as different parallel requests that are finalized once done.

Params prop that is set on the Destination or upload options is serialized (encoded according to Tus protocol) and sent as the value of the Upload-Metadata header.

Custom headers set on the Destination will be sent (and override existing headers) with the Creation request

Feature Detection

When the featureDetection option is enabled, the tus-sender will request the supported extensions' info from the server.

In case there are options that aren't supported by the extensions list the server provides, they will be turned off.

These options are:

• parallel: requiring the concatenation extension
• sendDataOnCreate: requiring the creation_with_upload extension
• deferLength: requiring the creation_defer_length extension

When onFeaturesDetected callback is provided, the responsibility to turn off options that aren't supported is handed over to the callback. The object returned by the callback will be merged with options being used, overriding them as needed.

For feature detection to work, when the TUS server is served from a different origin than the page making the request, the server must allow these headers: Tus-Extension and Tus-Version to be read over CORS. Otherwise, it will not work and feature detection will be skipped.

Example

import React, { useCallback, useEffect, useRef } from "react";
import createUploader from "@rpldy/uploader";
import getTusEnhancer from "@rpldy/tus-sender";

export const App = () => {
	const inputRef = useRef(null);
	const uploaderRef = useRef(null);

	useEffect(() => {
		const tusEnhancer = getTusEnhancer({
            parallel: 2,                
		});

		uploaderRef.current = createUploader({
			enhancer: tusEnhancer,
			destination: {url: "my-tus-server.com"},
			params: {
				source: "rpldy",		
			}
		});
	}, []);

	const onClick = useCallback(() => {
		const input = inputRef.current;
		if (input) {
			input.value = "";
			input.click();
		}
	}, []);

	const onInputChange = useCallback(() => {
		uploaderRef.current?.add(inputRef.current?.files);
	}, []);

	return <div>
		<input type="file" ref={inputRef} style={{ display: "none" }} onChange={onInputChange}/>
		<button id="upload-button" onClick={onClick}>Upload with TUS</button>
	</div>
};

Events

The TUS Sender exposes a RESUME_START event. See uploader events section on more info regarding how to register for events.

TUS_EVENTS.RESUME_START

Triggered before the (HEAD) request is issued on behalf of a potentially resumeable upload.

This event is cancellable

The event handler receives a ResumeStartEventData object