doc: update README and comments

    codecOptions: new CodecOptions({

        profile: TinyH264Decoder.maxProfile,

        level: TinyH264Decoder.maxLevel,

    })

})

    }),

});

```

However, it can fail on some very old devices that doesn't support even Baseline level 4 codec. You can retry without the `codecOptions` option if that happens.

### Render the video

It draws frames onto `decoder.element` (a `<canvas>` element), you can insert it anywhere you want to display the video.

It draws frames onto `decoder.renderer` (a `<canvas>` element), you can insert it anywhere you want to display the video.

```ts

const decoder = new TinyH264Decoder();

document.body.appendChild(decoder.element);

document.body.appendChild(decoder.renderer);

videoPacketStream // from `@yume-chan/scrcpy`

    .pipeTo(decoder.writable)

{

    "name": "@yume-chan/scrcpy-decoder-tinyh264",

    "version": "0.0.17",

    "description": "TypeScript implementation of Scrcpy.",

    "description": "Raw H.264 stream decoder and renderer wrapping TinyH264 and YUVCanvas packages (software decoding).",

    "keywords": [

        "adb",

        "android-phone",

## Usage

It draws frames onto `decoder.element` (a `<canvas>` element), you can insert it anywhere you want to display the video.

It draws frames onto `decoder.renderer` (a `<canvas>` element), you can insert it anywhere you want to display the video.

```ts

const decoder = new WebCodecsDecoder();

document.body.appendChild(decoder.element);

document.body.appendChild(decoder.renderer);

videoPacketStream // from `@yume-chan/scrcpy`

    .pipeTo(decoder.writable)

{

    "name": "@yume-chan/scrcpy-decoder-webcodecs",

    "version": "0.0.17",

    "description": "TypeScript implementation of Scrcpy.",

    "description": "Raw H.264 stream decoder and renderer using WebCodecs API (requires modern browser).",

    "keywords": [

        "adb",

        "android-phone",

# @yume-chan/stream-extra

Some useful extensions for Web Streams API.

Some useful extensions for working with binary streams. Conforms to the [Web Streams API](https://streams.spec.whatwg.org/).

Currently it's using [web-streams-polyfill](https://github.com/MattiasBuelens/web-streams-polyfill) because it's hard to load native implementations from both browsers and Node.js. (An experimental implementation using Top Level Await is available in `native.ts`, but not exported).

## Find an implementation

If all of `ReadableStream`, `WritableStream` and `TransformStream` fields are available on `globalThis`, they will be used. Otherwise, the [web-streams-polyfill](https://github.com/MattiasBuelens/web-streams-polyfill) package will be used.

Google Chrome 89 and Mozilla Firefox 102 provide full support for Web Streams API natively.

In Node.js, it's not possible to load the `stream/web` module while keeping the compatibility with both Web and bundlers:

-   Webpack has poor support with Top Level Await, for example, Hot Module Replacement doesn't work when any module is using TLA.

-   Web doesn't have the `module` module, thus requires a shim in import map.

Assigning `ReadableStream`, `WritableStream` and `TransformStream` from `stream/web` module to `globalThis`, before loading this library, will still work. Other custom polyfill can also be loaded this way.

## Compatibility issue with `ReadableStream#pipeTo` and `ReadableStream#pipeThrough`

The [Web Streams API spec](https://streams.spec.whatwg.org/#readable-stream-pipe-to) specifies that `ReadableStream#pipeTo` must check the argument to be an instance of `WritableStream`, so it can optimize the performance by calling internal methods directly.

Native implementations will perform this check, so `new globalThis.ReadableStream().pipeTo(new Polyfill.WritableStream())` will throw an error.

The `WrapReadableStream` class can be used to bypass this check:

```ts

import { WrapReadableStream } from "@yume-chan/stream-extra";

import { WritableStream as PolyfillWritableStream } from "web-streams-polyfill";

const nativeReadable = new globalThis.ReadableStream();

const wrappedReadable = new WrapReadableStream(new globalThis.ReadableStream());

nativeReadable.pipeTo(new PolyfillWritableStream()); // Error

wrappedReadable.pipeTo(new PolyfillWritableStream()); // OK

```

web-streams-polyfill package's `ReadableStream#pipeTo` only uses public methods, so it can be used with any `WritableStream` implementation.

## `BufferedReadableStream`