All Versions
20
Latest Version
Avg Release Cycle
-
Latest Release
-

Changelog History
Page 2

  • v0.9.2 Changes

    Other Changes

    • 🚚 Server: Remove content-length response header. @LeonSha in #385
    • 🌐 Server: Don't block on writing to the close notify channel. @devnev in #403
    • 📚 Documentation: Remove reference to specific release version in grpcwebproxy README. @l4u in #370
    • 📚 Documentation: Fix up problems present in the grpc-web-react-example project. @atecce in #360
    • 📚 Documentation: Updated the installation instructions of grpcwebproxy. @enmasse in #399

  • v0.9.1 Changes

    Other Changes

    • 🌐 Server: Ensure headers from wrapped server are forwarded appropriately. @danilvpetrov in #359

  • v0.9.0 Changes

    💥 Breaking Changes

    • 0️⃣ Server: Deny CORS Requests by Default. @jonny-improbable in #158
      • By default both the grpcweb in-process proxy and the standalone grpcwebproxy binary will deny any requests that come from (sub)domains that differ from that which the server is hosted on. See related docs for the in-process proxy here and for the standalone grpcwebproxy here.

    Other Changes

    • 🌐 Server: Support client certs for backend connections. [@mastersingh24] in #333

  • v0.8.0 Changes

    💥 Breaking Changes

    • 📦 Scoped npm package under the @improbable-eng org; consumers should now npm install @improbable-eng/grpc-web.

  • v0.7.0 Changes

    💥 Breaking Changes

    • ✂ Removed built-in support for NodeJS Environments; if you want to use grpc-web-client in a NodeJS environment you will need to import grpc-web-node-http-transport and specify it as your Default Transport.
    • 👀 The transport property passed to unary(), invoke() and client() should now be an instance of the Transport interface (was a reference to a factory function which returned a Transport instance), see #265 for details.

    Other Changes

    • 0️⃣ Client: Added grpc.setDefaultTransport() which can be used to specify which Transport is used when none is specified with the request. @jonny-improbable in #265
    • 🔧 Client: Allowed for configuration of XHR and Fetch-based transports and exposed them via the grpc namespace. @jonny-improbable in #265
    • 🌐 Client: Don't call callbacks if close() is called. @virtuald in #258
    • 🌐 Client: Export grpc-web-client as a UMD Module. @Dig-Doug in #276
    • 🌐 Server: Fix gRPC Web spec violation related to header/trailer names. @ktr0731 in #271
    • Server: Add backend_backoff_max_delay flag to grpcwebproxy. @fordhurley in #278
    • 0️⃣ Server: Add support for specifying a default :authority header for backend calls. @sandersaares in #267
    • 🌐 Server: Prevent leaking goroutines from websocket connections. @amerry in #253
    • 🌐 Server: Add option to increase max message size. @nevi-me in #246
    • 🌐 Server: Switched to assign CAs to correct config property. @jonahbron in #244

  • v0.6.3 Changes

    • 🛠 Fix callbacks being invoked after cancellation @mwei0210 in #207
    • 🛠 Fix unhandled promise rejection upon errors in fetch transport @Runar1 in #189
    • 🛠 Fix bug in gprcwebproxy's WebSocket Transport support @bianbian-org in #211
    • 🛠 Fix headers/trailers being lost when grpc-status is non-zero @gunn4r in #226

  • v0.6.2 Changes

    • ➕ Add support for WebSocket Transport in grpcwebproxy @JCGrant in #180

  • v0.6.1 Changes

    • 🛠 Fix gRPC message decoding @ishitatsuyuki in #117
    • ⚡️ Update the localhost certificate generation to create certs from a local certificate authority. @absoludity in #169
    • 🛠 Fix memory leak in fetch transport @nathanb21 in #184
    • ➕ Add abort signal support in fetch transport @Runar1 in #173

  • v0.6.0 Changes

  • v0.5.0 Changes

    • 🔨 Refactored client interface to provide a stronger abstraction for alternative Transports (ie: WebSockets) @MarcusLongmuir in #132
    • Everything is now exported under a single namespace (grpc).