February 04, 2025

@graphql-tools/[email protected]

Major Changes

• #481 0b13cb4 Thanks @enisdenjo! - Executor options don't exist graphql-ws dependency options

  Removing the dependency on the types. Some options are still exposed, but if you want to further customise the graphql-ws client, you should pass your own instance of the client instead.

  import { buildGraphQLWSExecutor } from '@graphql-tools/executor-graphql-ws';
  import { createClient } from 'graphql-ws';
  import { options } from './my-graphql-ws-client-options';
  
  const executor = buildGraphQLWSExecutor(
    createClient({
      url: 'ws://localhost:4000/graphql',
      ...options,
    }),
  );

• #481 0b13cb4 Thanks @enisdenjo! - Upgrade graphql-ws to v6

  If you have a custom graphql-ws configuration when building the executor with buildGraphQLWSExecutor, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.

Minor Changes

• #481 0b13cb4 Thanks @enisdenjo! - Export GraphQLWSExecutorOptions type

Patch Changes

• #481 0b13cb4 Thanks @enisdenjo! - dependencies updates:

  • Updated dependency graphql-ws@^6.0.3 ↗︎ (from ^5.14.0, in dependencies)

@graphql-hive/[email protected]

Patch Changes

• #481 0b13cb4 Thanks @enisdenjo! - dependencies updates:

  • Updated dependency graphql-ws@^6.0.3 ↗︎ (from ^5.16.0, in dependencies)

• #481 0b13cb4 Thanks @enisdenjo! - WebSocket transport options allow configuring only connectionParams

  In most of the cases you won't need to configure the underlying graphql-ws client any further.

• #481 0b13cb4 Thanks @enisdenjo! - Upgrade graphql-ws to v6

  If you have a custom graphql-ws configuration when using the transport, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.

• Updated dependencies [0b13cb4, 0b13cb4, 0b13cb4, 0b13cb4, 0b13cb4]:

  • @graphql-hive/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

@graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [0b13cb4]:
  • @graphql-hive/[email protected]

@graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [0b13cb4]:
  • @graphql-hive/[email protected]

@graphql-hive/[email protected]

Patch Changes

• #481 0b13cb4 Thanks @enisdenjo! - dependencies updates:

  • Updated dependency graphql-ws@^6.0.3 ↗︎ (from ^5.16.0, in dependencies)

• Updated dependencies []:

  • @graphql-mesh/[email protected]

@graphql-mesh/[email protected]

Major Changes

• #481 0b13cb4 Thanks @enisdenjo! - WebSocket transport options allow configuring only connectionParams

  In most of the cases you won't need to configure the underlying graphql-ws client any further.

• #481 0b13cb4 Thanks @enisdenjo! - WebSocket transport is stable and production ready

Minor Changes

• #481 0b13cb4 Thanks @enisdenjo! - Upgrade graphql-ws to v6

  If you have a custom graphql-ws configuration when using the transport, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.

Patch Changes

• #481 0b13cb4 Thanks @enisdenjo! - dependencies updates:

  • Updated dependency graphql-ws@^6.0.3 ↗︎ (from ^5.16.0, in dependencies)
  • Added dependency isomorphic-ws@^5.0.0 ↗︎ (to dependencies)

• Updated dependencies [0b13cb4, 0b13cb4, 0b13cb4, 0b13cb4]:

  • @graphql-tools/[email protected]