v0.4.0

This release includes the following:

Enhancements

• Upgrade to protobuf-es v0.5.0 by @smaye81 in #373

v0.3.3

This release includes the following:

Enhancements

• Upgrade to protobuf-es v0.4.0 by @smaye81 #361

v0.3.2

This release includes the following:

Enhancements

• Upgrade to protobuf-es v0.3.0 by @smaye81 #337

v0.3.1

Enhancements

• Upgrade to protobuf-es v0.2.1 by @smaye81 #309

v0.3.0

Enhancements

• Upgrade to protobuf-es v0.2.0 by @smaye81 #292
• Respect binary encoding options in the connect transport by @timostamm #274
• Deprecate ConnectError constructor by @timostamm #272

Bugfixes

• Fix await res.json() in package README by @timostamm #269
• Fix await res.json() in top-level README by @nguyenyou #268
• Fix: raise a ConnectError with Code.Canceled from StreamResponse.read() by @timostamm #267

New Contributors

@nguyenyou made their first contributions in #268

v0.2.1

Documentation

• Fix protoc option in protoc-gen-connect-web/README.md by @ymmt2005 in #258

Bug Fixes

• Fixes type prop in conditional exports by @smaye81 in #248. This adds support for TypeScript compiler option of moduleResolution: "NodeNext".

New Contributors

@ymmt2005 made their first contribution in #258.

v0.2.0

Enhancements

• Add automated browser tests and BrowserStack integration by @timostamm in #243.
• Updates dependencies for protobuf-es packages by @smaye81 in #242. Note that this includes important bugfixes in protobuf-es 0.1.0. See the release there for more details.
• Point to CommonJS in entrypoint by @smaye81 in #237.
• Add example project to show usage of connect-web by @timostamm in #215.
• Add code generation examples to protoc-gen-connect-web README.md by @timostamm in #240.
• Switch from deprecated TypeRegistry to createRegistry() by @timostamm in #225.

Bug Fixes

• Fix streams lagging behind by @timostamm in #235. Special thanks to @aslatemts for catching the bug and suggesting a fix.

New Contributors

@vipero07 made their first contribution in #232

v0.1.0

This release implements a change in the Connect protocol, regarding how error details are encoded. The change is backwards-incompatible. Connect-Web is not able to decode error details from connect-go v0.2.0 and earlier.

• Accept error details as binary (#202)

Aside from that, we made two small improvements to the developer experience:

• Trim trailing slash in transport option "baseUrl" (#205)
• Be explicit about Node.js support (#206)

v0.0.10

This release includes a breaking change: Error details are now accessible with the new connectErrorDetails() function, and no longer via Error.details.

• Port the code generator to TypeScript (#196)
• Add main prop for older webpack support (#167)
• Improve error details API (#164)
• Export transport options (#169)
• Clarify TypeScript compatibility (#190)

v0.0.9

• Fix gRPC-web unary trailers-only response handling (#148)
• Return the AsyncIterable directly from the ServerStreamingFn (#139)
• Update to protobuf-es v0.0.7 (#147)