You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: javascript(-web) should specify protobuf as a peer dependency (#……317)
Similar to #315, protobuf should be a peer dependency in the
JavaScript projects. Since the SDKs install protobuf alongside grpc,
it is vulnerable to the same deduplication problem as we had with
grpc.
chore: specify javascript grpc dependencies as peer dependencies (#315)
Because the JavaScript SDKs must also have the grpc
library (`@grpc/grpc-js` for node; `grpc-web` for web) installed, the
proto libraries here should declare those as peer dependencies, not
production dependencies.
In the previous form as production dependencies, both the SDK and the
protos libraries would have grpc as a dependency. In some situations
those dependencies do not deduplicate. Because we create grpc symbols
in the SDK to pass to objects from the protos library, those symbols
will not pass `instanceof` checks when deduplication fails.
By mandating grpc as a peer dependency, we avoid this
altogether. There will be one copy of grpc to load between the SDK and
the protos library: the one the SDK installs.
chore: clean up javascript and javascript web dependencies (#314)
The javascript package.json listed both grpc-tools and
protoc-gen-ts as production dependencies, when they are only build
dependencies. This impacts users deploying to Lambda who are sensitive
to the package size.
Javascript-web also contained protobuf as both a production and dev
dependency. We removed it as a dev dependency.
feat: new apis to check-and-set an item based on a hash (#312)
* feat: new apis to check-and-set an item based on value hashes
* fix: update hacky js-web script to handle new messages
* chore: rename for clarity