The passed stream is wrapped in `it-handshake` which can derive the
unwrapped type from the input.  This module assumes `TSink` will be
`Uint8Array` which may not be the case.

Instead, derive the unwrapped stream type from the input, though it's
meant needing to make the `ProtobufStream` type generic which may
trip up certain use cases (declaring a `ProtobufStream` variable, for
example) so this is a breaking change.

BREAKING CHANGE: The ProtobufStream type is now generic - it can be inferred from the return type of `pbStream` but may need to be specified where it it accepted as an argument

## [3.0.0](v2.0.4...v3.0.0) (2023-02-23)

### ⚠ BREAKING CHANGES

* The ProtobufStream type is now generic - it can be inferred from the return type of `pbStream` but may need to be specified where it it accepted as an argument

### Bug Fixes

* derive unwrapped stream type from input ([#39](#39)) ([e85d75e](e85d75e))

What we want to say is that the type returned from `unwrap` will be
the original duplex passed in, but it's source will have changed to
return `Uint8ArrayList`s.  We can still pass duplexes that source
`Uint8Array`s though, so make the exported function polymorphic.

## [3.0.1](v3.0.0...v3.0.1) (2023-03-01)

### Bug Fixes

* make pbStream function polymorphic ([#40](#40)) ([ccb2065](ccb2065))

…ier (#41)

Exports a type for the return value of `stream.pb`

## [3.1.0](v3.0.1...v3.1.0) (2023-03-04)

### Features

* add MessageStream type to make dealing with message streams easier ([#41](#41)) ([c1fa76a](c1fa76a))

Adds an unwrap method to messages streams to access the underlying protobuf stream

## [3.2.0](v3.1.0...v3.2.0) (2023-03-06)

### Features

* allow unwrapping message stream ([#42](#42)) ([f2169fe](f2169fe))