connect-es

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)

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)

• 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)

This is the second release with support of the Connect protocol, with several breaking changes to streamline and improve the API.

Breaking changes:

• Clean up the Connect protocol implementation (#30)
• Move json conversion functions to standalone (#132)

Bug fixes:

• Use target es2017 (#129)

This is the first release with support for the Connect protocol, and has a few breaking changes. Most importantly, createConnectTransport() now creates a transport that uses the Connect protocol instead of gRPC-web. To use gRPC-web, switch to createGrpcWebTransport().

New features:

• Implement Connect (#94)
• Add makeAnyClient() (#106)
• Add mergeHeaders() (#109)
• Surface response metadata in errors (#100)

Breaking changes:

• Implement Connect (#94)
• Drop clients with exact requests (#105)
• Rename timeout option to timeoutMs (#103)
• Delete StatusCode.Ok and rename StatusCode to Code (#101)

Bug fixes:

• Fix CommonJS exports of @bufbuild/connect-web (#116)
• Fix typing in generated *_connect_web.d.ts (#107)