js-sdk-contrib
js-sdk-contrib copied to clipboard
open-feature
fix(deps): update dependency @connectrpc/connect to v2
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @connectrpc/connect (source) | ^1.4.0 -> ^2.0.0 |
Release Notes
connectrpc/connect-es (@connectrpc/connect)
v2.0.1
What's Changed
The only noteworthy changes in this release are enhancements made to the @connectrpc/connect-migrate package.
The migration tool now handles additional scenarios for migrating your code to Connect v2:
Transforms new to create:
- import { Foo } from "./foo_pb.js";
+ import { FooSchema } from "./foo_pb.js";
+ import { create } from "@​bufbuild/protobuf";
- const foo = new Foo();
+ const foo = create(FooSchema);
Transforms isMessage to use the schema:
import { isMessage } from "@​bufbuild/protobuf";
- import { Foo } from "./foo_pb.js";
+ import { FooSchema } from "./foo_pb.js";
- isMessage(1, Foo);
+ isMessage(1, FooSchema);
Transforms the static fromBinary, fromJson, and fromJsonString method calls:
- import { Foo } from "./foo_pb.js";
+ import { FooSchema } from "./foo_pb.js";
+ import { fromJson } from "@​bufbuild/protobuf";
- Foo.fromJson(x, y);
+ fromJson(FooSchema, x, y);
In addition, if the message is a well-known type, the import path is updated accordingly.
For details on Connect v2, see the v2 release notes as well as the full migration guide.
- Transform class references in connect-migrate by @timostamm and @smaye81 in https://github.com/connectrpc/connect-es/pull/1342
New Contributors
- @HermanBilous made their first contribution in https://github.com/connectrpc/connect-es/pull/1340
Full Changelog: https://github.com/connectrpc/connect-es/compare/v2.0.0...v2.0.1
v2.0.0
What's Changed
- We're upgrading to Protobuf-ES version 2. It's the largest change in this release.
- Connect-ES no longer needs its own code generator plugin.
- We're adding support for Next.js 15, Fastify 5, and Express 5.
- We're dropping support for old versions of Node.js and TypeScript. You'll need at least Node.js 18.14.1 and TypeScript 4.9.6.
The upgrade of the Protobuf runtime brings support for Editions and new APIs for Protobuf messages with support for custom options. Messages are now plain TypeScript types, which greatly improves compatibility with the ecosystem. For example, messages can be passed from a server-side component in Next.js to a client-side component without losing any data or types. To learn more about the enhancements, see the release blog post for Protobuf-ES v2.
[!TIP] If you are already using Connect, see our migration guide to upgrade to version 2.
Full Changelog
- Support Fastify v5 in @connectrpc/connect-fastify by @timostamm in https://github.com/connectrpc/connect-es/pull/1296
- Support Express v5 in @connectrpc/connect-fastify by @timostamm in https://github.com/connectrpc/connect-es/pull/1297
- Add support for Next.js v15 by @timostamm in https://github.com/connectrpc/connect-es/pull/1290
- Allow user-provided User-Agent request header by @polRk in https://github.com/connectrpc/connect-es/pull/1272
- Ensure that a signal exists for a completed RPC by @timostamm in https://github.com/connectrpc/connect-es/pull/1282
- Require HTTP/2 for the gRPC transport by @timostamm in https://github.com/connectrpc/connect-es/pull/1279
- Replace MethodInfo with Descriptor Types by @srikrsna-buf in https://github.com/connectrpc/connect-es/pull/1255
- Remove "credentials" option from transports by @timostamm in https://github.com/connectrpc/connect-es/pull/1242
- Remove
createPromiseClientandPromiseClientby @srikrsna-buf in https://github.com/connectrpc/connect-es/pull/1240 - Bump minimum supported TypeScript version to 4.9.5 by @timostamm in https://github.com/connectrpc/connect-es/pull/1231
- Remove support for Node.js v16 by @timostamm in https://github.com/connectrpc/connect-es/pull/1225
- Remove Node10 subpath fallbacks by @timostamm in https://github.com/connectrpc/connect-es/pull/1227
- Remove protoc-gen-connect-es by @timostamm in https://github.com/connectrpc/connect-es/pull/1224
- Swith to protobuf v2 by @srikrsna-buf in https://github.com/connectrpc/connect-es/commit/4fa60c80cb0832150f8c2798b0bb06c3406ca311
Full Changelog: https://github.com/connectrpc/connect-es/compare/v1.6.1...v2.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
⚠️ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @bufbuild/[email protected]
npm error node_modules/@bufbuild/protobuf
npm error @bufbuild/protobuf@"^1.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bufbuild/protobuf@"^2.2.0" from @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error @connectrpc/connect@"^2.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-06-23T16_41_11_725Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-23T16_41_11_725Z-debug-0.log
File name: libs/providers/flagd-web/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @openfeature/[email protected]
npm error Found: @bufbuild/[email protected]
npm error node_modules/@bufbuild/protobuf
npm error @bufbuild/protobuf@"^1.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bufbuild/protobuf@"^2.2.0" from @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error @connectrpc/connect@"^2.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-06-23T16_41_15_140Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-23T16_41_15_140Z-debug-0.log
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.