Update dependency @bufbuild/connect-web to v0.12.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@bufbuild/connect-web	0.8.6 -> 0.12.0

---

Release Notes

bufbuild/connect-es (@​bufbuild/connect-web)

v0.12.0

Compare Source

v0.11.0

Compare Source

What's Changed

Disregard non-JSON error response bodies for unary requests

This release makes a change in how response bodies are parsed for Connect unary requests that result in an HTTP error. Previously, all response bodies for unary requests that returned an HTTP error status were parsed with response.json(). However, this could lead to errors with non-JSON bodies. Now, only responses with a Content-Type of application/json will have the body parsed as JSON and added to the resulting Connect error.

For all other errors, the resulting Connect error will show the HTTP status code as the message and the corresponding Connect error code as the code.

To reiterate, this only affects Connect protocol unary requests that end with an HTTP error status code. All other protocols and/or RPC types are unaffected.

Enhancements

• https://github.com/bufbuild/connect-es/pull/686
• https://github.com/bufbuild/connect-es/pull/692
• https://github.com/bufbuild/connect-es/pull/695

New Contributors

• @​akosyakov made their first contribution in https://github.com/bufbuild/connect-es/pull/686

Full Changelog: connectrpc/connect-es@v0.10.1...v0.11.0

v0.10.1

Compare Source

What's Changed

• Handle GOAWAY frames with NO_ERROR in Node.js clients by @​timostamm in https://github.com/bufbuild/connect-es/pull/681

Full Changelog: connectrpc/connect-es@v0.10.0...v0.10.1

v0.10.0

Compare Source

What's Changed

KeepAlive

As of this release, Connect-ES offers Basic Keepalive support for HTTP/2 for clients that use one of the transports from @bufbuild/connect-node. Note that this replaces the option keepSessionAlive, which is deprecated with this PR.

In it's most simple form, the following example enables regular PINGs every 5 minutes:

import { createConnectTransport } from "@​bufbuild/connect-node";

const transport = createConnectTransport({
  httpVersion: "2",
  baseUrl: "https://demo.connect.build",
  pingIntervalMs: 1000 * 60 * 5,
});

For more information, see https://github.com/bufbuild/connect-es/pull/673

JSON parser ignores unknown fields by default

This release also changes the default behavior of the JSON parser so that unknown fields are ignored rather than rejected. Previously, Connect-ES followed the official guidance of the proto3 language spec and rejected unknown fields by default in parsing. However, this contradicts with the ethos that adding fields to a Protobuf definition should not be a breaking change. Therefore, the default behavior has been changed so any new/unknown fields are simply ignored.

Note that this could be considered a breaking change if consumers were relying on this rejection behavior.

Enhancements

• Manage HTTP/2 connections and keep them alive with PING frames by @​timostamm in https://github.com/bufbuild/connect-es/pull/673
• Ignore unknown JSON fields by default by @​timostamm in https://github.com/bufbuild/connect-es/pull/642
• Modify parsing of response for Connect unary requests by @​smaye81 in https://github.com/bufbuild/connect-es/pull/668

Full Changelog: connectrpc/connect-es@v0.9.1...v0.10.0

v0.9.1

Compare Source

What's Changed

• Avoid circular dependencies by @​fubhy in https://github.com/bufbuild/connect-es/pull/645
• Allow HTTP 204 response in the gRPC-web client by @​timostamm in https://github.com/bufbuild/connect-es/pull/656

Full Changelog: connectrpc/connect-es@v0.9.0...v0.9.1

v0.9.0

Compare Source

What's Changed

As of this release, connect-es supports performing idempotent, side-effect free requests using HTTP GETs. This makes it easier to cache responses in the browser, on your CDN, or in proxies and other middleboxes.

Note
This functionality is only supported when using the Connect protocol—using a Connect client with a Connect server. When using any gRPC or gRPC-web client, including createGrpcTransport() and createGrpcWebTransport() from @​bufbuild/connect-web or @​bufbuild/connect-node, all requests will continue to be HTTP POSTs.

To opt into GET support for a given Protobuf RPC, you must mark it as being side-effect free using the MethodOptions.IdempotencyLevel option:

service ElizaService {
  rpc Say(stream SayRequest) returns (SayResponse) {
    option idempotency_level = NO_SIDE_EFFECTS;
  }
}

With this schema change, handlers will automatically support both GET and POST requests for this RPC. However, clients will continue to use POST requests by default, even when GETs are possible. To make clients use GETs for side effect free RPCs, set the useHttpGet option:

const transport = createConnectTransport({
  // ...
  useHttpGet: true
});

Another noteworthy change is the full support of timeouts, also known as deadlines in gRPC. For example, when a client provides the timeoutMs call option, a header Connect-Timeout-Ms is added to the request. The server parses this timeout, and if it takes longer than the given timeout to process the request, it should give up, and respond with the error code deadline_exceeded.

On a connect-es server, the parsed timeout is available as an AbortSignal on the context:

import type { HandlerContext } from "@​bufbuild/connect";

const say = async (req: SayRequest, ctx: HandlerContext) => {

  ctx.signal.aborted; // true if timed out
  ctx.signal.reason; // an error with code deadline_exceed if timed out
  ctx.timeoutMs(); // the remaining time in milliseconds

  // raises an error with code deadline_exceed if timed out
  ctx.signal.throwIfAborted();

  // the AbortSignal can be passed to other functions
  await longRunning(ctx.signal);

  return new SayResponse({sentence: `You said: ${req.sentence}`});
};

Enhancements

• Add client support for Connect HTTP GET requests by @​jchadwick-buf in https://github.com/bufbuild/connect-es/pull/620
• Add server support for Connect HTTP GET requests by @​jchadwick-buf in https://github.com/bufbuild/connect-es/pull/624
• Allow a fetch override for connect-web by @​dimitropoulos in https://github.com/bufbuild/connect-es/pull/618
• Support timeouts in clients by @​timostamm in https://github.com/bufbuild/connect-es/pull/635
• Support timeouts in handlers by @​timostamm in https://github.com/bufbuild/connect-es/pull/591
• Update HandlerContext signal to trigger on other reasons than timeouts by @​johynpapin in https://github.com/bufbuild/connect-es/pull/531
• Add a timeout getter to the HandlerContext and export createHandlerContext by @​timostamm in https://github.com/bufbuild/connect-es/pull/632
• Add from() and findDetails() to ConnectError by @​timostamm in https://github.com/bufbuild/connect-es/pull/638
• Always generate files when no services exist by @​sjbarag in https://github.com/bufbuild/connect-es/pull/598

Bugfixes

• Fix UniversalHandlers resolving the response before headers are complete by @​timostamm in https://github.com/bufbuild/connect-es/pull/588
• Improve tests for Node.js clients and fix hanging requests by @​timostamm in https://github.com/bufbuild/connect-es/pull/619
• Indent "idempotency" in protoc-gen-connect-es by @​timostamm in https://github.com/bufbuild/connect-es/pull/626
• Close the session on error in client transports by @​timostamm in https://github.com/bufbuild/connect-es/pull/623
• Raise proper Connect error codes for closed streams in handlers by @​timostamm in https://github.com/bufbuild/connect-es/pull/628
• Support client-side cancellation in the router transport by @​timostamm in https://github.com/bufbuild/connect-es/pull/637

Breaking changes

• Remove deprecated exports from connect-web by @​smaye81 in https://github.com/bufbuild/connect-es/pull/636
• Stop supporting Node.js earlier than v16 in protoc-gen-es by @​dimitropoulos in https://github.com/bufbuild/connect-es/pull/614

New Contributors

• @​bufdev made their first contribution in https://github.com/bufbuild/connect-es/pull/593
• @​sjbarag made their first contribution in https://github.com/bufbuild/connect-es/pull/598

Full Changelog: connectrpc/connect-es@v0.8.6...v0.9.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.