Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@graphql-tools/executor-graphql-ws

graphql-hive10.1mMIT1.3.7TypeScript support: included

A set of utils for faster development of GraphQL tools

readme

Hive GraphQL Platform

Hive Gateway

A fully open-source MIT-licensed GraphQL API gateway that can act as a GraphQL federation Gateway or a Proxy Gateway for any GraphQL services.

It can be run as a standalone binary, a Docker Image, or as a JavaScript package (e.g. within Node.js, Bun, Deno, Google Cloud Functions, Azure Functions or Cloudflare Workers)

changelog

@graphql-tools/executor-graphql-ws

1.3.7

Patch Changes

  • #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

    Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request. Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query. For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

    With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

    For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

    -import { print } from 'graphql';
    -const query = print(parsedQuery);
    +import { defaultPrintFn } from '@graphql-tools/executor-common';
    +const query = defaultPrintFn(parsedQuery);

    Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

    -const serializedRequest = {
    -  query: print(executionRequest.document),
    -  variables: executionRequest.variables,
    -  operationName: executionRequest.operationName,
    -  extensions: executionRequest.extensions,
    -};
    +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
    +const serializedRequest = serializeExecutionRequest(executionRequest);
  • Updated dependencies [55eb1b4]:

1.3.6

Patch Changes

1.3.5

Patch Changes

1.3.4

Patch Changes

1.3.3

Patch Changes

1.3.2

Patch Changes

1.3.1

Patch Changes

1.3.0

Minor Changes

1.2.1

Patch Changes

  • #6536 3facde0 Thanks @EmrysMyrddin! - webSocketImpl and lazy options were ignored and overriden by default values. This is no longer the case and it's now possible to change the WebSocket implementation.

1.2.0

Minor Changes

  • #6323 cacf20f Thanks @ardatan! - Implement Symbol.dispose or Symbol.asyncDispose to make `Executor`s `Disposable`

Patch Changes

1.1.2

Patch Changes

1.1.1

Patch Changes

  • #5666 6269314d Thanks @ThomasMoritz! - changed the order how the configuration is given into the graphql-wsclient and prevent the overwriting of the parameters

1.1.0

Minor Changes

1.0.2

Patch Changes

1.0.1

Patch Changes

1.0.0

Major Changes

Patch Changes

0.0.14

Patch Changes

0.0.13

Patch Changes

0.0.12

Patch Changes

0.0.11

Patch Changes

0.0.10

Patch Changes

0.0.9

Patch Changes

0.0.8

Patch Changes

0.0.7

Patch Changes

  • 1c291f33 Thanks @ardatan! - Support regular queries and mutations in WS Executor

0.0.6

Patch Changes

0.0.5

Patch Changes

0.0.4

Patch Changes

0.0.3

Patch Changes

0.0.2

Patch Changes

0.0.1

Patch Changes