Package detail

@graphql-mesh/fusion-runtime

graphql-hive63.3kMIT0.11.15

Runtime for GraphQL Mesh Fusion Supergraph

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-mesh/fusion-runtime

0.11.15

Patch Changes

0.11.14

Patch Changes

0.11.13

Patch Changes

  • #1113 88c9369 Thanks @ardatan! - Handle serving subgraphs when;
    • No entity is found
    • Query root type has a different name than Query
    • Federation transform by adding @key directive to a type but without a resolver
  • Updated dependencies [faffc17, 0512be3]:
    • @graphql-tools/batch-execute@9.0.16
    • @graphql-tools/delegate@10.2.18
    • @graphql-tools/federation@3.2.2
    • @graphql-tools/stitch@9.4.23
    • @graphql-tools/stitching-directives@3.1.33
    • @graphql-tools/wrap@10.0.36

0.11.12

Patch Changes

  • #1095 2dc5fd8 Thanks @enisdenjo! - Provide non-GraphQL upstream service responses to the retry mechanism configuration

0.11.11

Patch Changes

0.11.10

Patch Changes

0.11.9

Patch Changes

  • #946 7d771d8 Thanks @ardatan! - dependencies updates:

  • #950 c7ea2c5 Thanks @kroupacz! - Errors should not be swallowed when it is thrown from the shared root

  • #946 7d771d8 Thanks @ardatan! - Fail when the fetcher returns an empty result. Previously even if fetcher returns undefined, the runtime was trying to handle the result then fails with a cryptic error

  • Updated dependencies [7d771d8, 7d771d8, c7ea2c5, 0af3485]:

    • @graphql-tools/federation@3.2.0
    • @graphql-tools/delegate@10.2.17
    • @graphql-tools/stitch@9.4.22
    • @graphql-mesh/transport-common@0.7.34
    • @graphql-tools/stitching-directives@3.1.32
    • @graphql-tools/wrap@10.0.35

0.11.8

Patch Changes

  • Updated dependencies [a374bfc]:
    • @graphql-mesh/transport-common@0.7.33

0.11.7

Patch Changes

0.11.6

Patch Changes

0.11.5

Patch Changes

0.11.4

Patch Changes

  • #818 115a1f1 Thanks @ardatan! - When the schema is reloaded during a query execution, retry the request instead of throwing a reload event error

0.11.3

Patch Changes

0.11.2

Patch Changes

0.11.1

Patch Changes

  • Updated dependencies [2318393]:
    • @graphql-tools/delegate@10.2.13
    • @graphql-tools/federation@3.1.3
    • @graphql-tools/stitch@9.4.18
    • @graphql-tools/stitching-directives@3.1.28
    • @graphql-tools/wrap@10.0.31

0.11.0

Minor Changes

  • #605 e5d77f3 Thanks @ardatan! - Extract subgraph execution batching logic outside, so batching is handled by the Gateway not Stitching

    BREAKING; UnifiedGraphHandlerOpts no longer takes batch option, it is handled by the runtime itself

Patch Changes

0.10.32

Patch Changes

  • #590 203172c Thanks @ardatan! - Refactor to make it easier to replace the supergraph execution

  • Updated dependencies [8c80ac9]:

    • @graphql-mesh/transport-common@0.7.28
    • @graphql-tools/federation@3.1.1

0.10.31

Patch Changes

  • #538 aab5441 Thanks @renovate! - dependencies updates:

  • Updated dependencies [b52c9ba, 9144222, b0bc26b]:

    • @graphql-tools/federation@3.1.0
    • @graphql-tools/delegate@10.2.11
    • @graphql-tools/stitch@9.4.16
    • @graphql-tools/stitching-directives@3.1.26
    • @graphql-tools/wrap@10.0.29

0.10.30

Patch Changes

  • Updated dependencies [18682e6, e9f78cd]:
    • @graphql-tools/delegate@10.2.10
    • @graphql-tools/wrap@10.0.28
    • @graphql-tools/federation@3.0.10
    • @graphql-tools/stitch@9.4.15
    • @graphql-tools/stitching-directives@3.1.25

0.10.29

Patch Changes

  • #420 14152f7 Thanks @ardatan! - dependencies updates:

  • #420 14152f7 Thanks @ardatan! - - In case of schema reload, throw SCHEMA_RELOAD error while recreating the transports and executors

    • In case of shut down, throw SHUTTING_DOWN error while cleaning the transports and executors up

    Previously, these errors are only thrown for subscriptions not it is thrown in other type of operations as well. And previously the thrown errors during these two cleanup and restart process were cryptic, now the mentioned two errors above are thrown with more clear messages

  • #420 14152f7 Thanks @ardatan! - Leave the supergraph configuration handling logic to fusion-runtime package so it can compare bare read supergraph sdl directly inside unified graph manager to decide if the supergraph has changed.

  • Updated dependencies [14152f7, a625269, a625269, 14152f7]:

    • @graphql-mesh/transport-common@0.7.27
    • @graphql-tools/stitch@9.4.14
    • @graphql-tools/federation@3.0.9

0.10.28

Patch Changes

  • Updated dependencies [0591aa9]:
    • @graphql-tools/federation@3.0.8

0.10.27

Patch Changes

  • Updated dependencies [3571399]:
    • @graphql-tools/federation@3.0.7
    • @graphql-mesh/transport-common@0.7.26
    • @graphql-tools/stitch@9.4.13

0.10.26

Patch Changes

  • Updated dependencies []:
    • @graphql-tools/stitch@9.4.12
    • @graphql-tools/federation@3.0.6

0.10.25

Patch Changes

  • Updated dependencies [55eb1b4, 55eb1b4]:
    • @graphql-mesh/transport-common@0.7.25
    • @graphql-tools/federation@3.0.5

0.10.24

Patch Changes

0.10.23

Patch Changes

  • #357 8b64103 Thanks @ardatan! - Fix the bug on setting the default polling interval to 10 seconds So by default, the gateway will poll the schema every 10 seconds, and update the schema if it has changed.

    This PR also contains improvements on logging about polling

0.10.22

Patch Changes

0.10.21

Patch Changes

  • Updated dependencies [23b8987, 23b8987]:
    • @graphql-mesh/transport-common@0.7.23
    • @graphql-tools/delegate@10.2.8
    • @graphql-tools/federation@3.0.2
    • @graphql-tools/stitch@9.4.10
    • @graphql-tools/stitching-directives@3.1.23
    • @graphql-tools/wrap@10.0.26

0.10.20

Patch Changes

  • Updated dependencies []:
    • @graphql-tools/federation@3.0.1

0.10.19

Patch Changes

  • Updated dependencies [d747d4c, d747d4c]:
    • @graphql-tools/federation@3.0.0

0.10.18

Patch Changes

0.10.17

Patch Changes

0.10.16

Patch Changes

0.10.15

Patch Changes

0.10.14

Patch Changes

  • #274 3f1a0fa Thanks @ardatan! - Improve `import` and `require` interop

  • Updated dependencies []:

    • @graphql-tools/federation@2.2.39

0.10.13

Patch Changes

0.10.12

Patch Changes

  • Updated dependencies [9ce705c]:
    • @graphql-tools/delegate@10.2.5
    • @graphql-tools/federation@2.2.37
    • @graphql-tools/stitch@9.4.7
    • @graphql-tools/stitching-directives@3.1.20
    • @graphql-mesh/transport-common@0.7.20
    • @graphql-tools/wrap@10.0.23

0.10.11

Patch Changes

0.10.10

Patch Changes

  • Updated dependencies []:
    • @graphql-tools/delegate@10.2.4
    • @graphql-tools/federation@2.2.35
    • @graphql-tools/stitch@9.4.5
    • @graphql-tools/stitching-directives@3.1.19
    • @graphql-mesh/transport-common@0.7.19
    • @graphql-tools/wrap@10.0.22

0.10.9

Patch Changes

  • #234 ba7e585 Thanks @ardatan! - Drop `@hidden` support in favor of `@inaccessible`

  • Updated dependencies [ba7e585]:

    • @graphql-tools/federation@2.2.34

0.10.8

Patch Changes

  • Updated dependencies [7ca0ff3]:
    • @graphql-tools/federation@2.2.33
    • @graphql-tools/delegate@10.2.3
    • @graphql-tools/stitch@9.4.4
    • @graphql-tools/stitching-directives@3.1.18
    • @graphql-mesh/transport-common@0.7.18
    • @graphql-tools/wrap@10.0.21

0.10.7

Patch Changes

0.10.6

Patch Changes

0.10.5

Patch Changes

  • Updated dependencies [725d5b7]:
    • @graphql-tools/federation@2.2.30
    • @graphql-tools/stitch@9.4.1

0.10.4

Patch Changes

0.10.3

Patch Changes

0.10.2

Patch Changes

  • Updated dependencies [eee53b9, eee53b9]:
    • @graphql-mesh/runtime@0.104.1
    • @graphql-mesh/utils@0.102.12
    • @graphql-mesh/types@0.102.12
    • @graphql-mesh/transport-common@0.7.13

0.10.1

Patch Changes

0.10.0

Patch Changes

  • Updated dependencies [ac82d44]:
    • @graphql-mesh/runtime@0.104.0

0.9.7

Patch Changes

0.9.6

Patch Changes

  • #7712 dc54d58 Thanks @EmrysMyrddin! - WebSocket connections are now cached against the whole connectionParams object and forwarded headers. The fixes WebSocket connection being reused wrongly when connectionParams.token is stable while other fields are changing.

0.9.5

Patch Changes

0.9.4

Patch Changes

  • #7816 fad4d27 Thanks @ardatan! - dependencies updates:

  • #7816 fad4d27 Thanks @ardatan! - Fix subscription fields fed by webhooks and defined in `additionalTypeDefs` with `@resolveTo`

  • Updated dependencies [fad4d27]:

    • @graphql-mesh/utils@0.102.9
    • @graphql-mesh/runtime@0.103.10
    • @graphql-mesh/types@0.102.9
    • @graphql-mesh/transport-common@0.7.10

0.9.3

Patch Changes

0.9.2

Patch Changes

0.9.1

Patch Changes

0.9.0

Minor Changes

0.8.14

Patch Changes

  • Updated dependencies [bf588d3]:
    • @graphql-mesh/utils@0.102.6
    • @graphql-mesh/runtime@0.103.7
    • @graphql-mesh/types@0.102.6
    • @graphql-mesh/transport-common@0.7.7

0.8.13

Patch Changes

0.8.12

Patch Changes

  • #7676 adc3293 Thanks @ardatan! - If the target hoisted field is a new field name that doesn't exist, create that field and keep the existing one;

    createHoistFieldTransform({
      mapping: [
        {
          typeName: 'Query',
          pathConfig: ['users', 'results'],
          newFieldName: 'usersResults',
        },
      ],
    });
    
    type Query {
      users(limit: Int!, page: Int): UserSearchResult # Keep this
    + usersResults(limit: Int!, page: Int): [User!]! # Add a new one
    }
    
    scalar _HoistConfig
    
    type UserSearchResult {
      page: Int!
    }
    
    type User {
      id: ID!
      name: String!
    }
    

0.8.11

Patch Changes

0.8.10

Patch Changes

0.8.9

Patch Changes

0.8.8

Patch Changes

  • Updated dependencies [7df3815]:
    • @graphql-mesh/runtime@0.103.6

0.8.7

Patch Changes

0.8.6

Patch Changes

0.8.5

Patch Changes

  • Updated dependencies [5146df0]:
    • @graphql-mesh/transport-common@0.7.5

0.8.4

Patch Changes

0.8.3

Patch Changes

  • #7572 14ec31f Thanks @ardatan! - dependencies updates:

  • #7569 e9d73b7 Thanks @ardatan! - If the first poll fails, keep polling but fail on requests If any poll fails in somewhere, keep polling but keep using the last successful supergraph

    So if the CDN is down at some point, the gateway will keep polling the supergraph, but will keep using the last successful supergraph. This is useful for cases where the CDN is down, but the supergraph is still available.

  • Updated dependencies [14ec31f, 14ec31f, 14ec31f, 14ec31f]:

    • @graphql-mesh/runtime@0.103.3
    • @graphql-mesh/transport-common@0.7.3
    • @graphql-mesh/types@0.102.3
    • @graphql-mesh/utils@0.102.3

0.8.2

Patch Changes

0.8.1

Patch Changes

0.8.0

Patch Changes

  • Updated dependencies [db41f96]:
    • @graphql-mesh/types@0.102.0
    • @graphql-mesh/runtime@0.103.0
    • @graphql-mesh/utils@0.102.0
    • @graphql-mesh/transport-common@0.7.0

0.7.3

Patch Changes

0.7.2

Patch Changes

0.7.1

Patch Changes

0.7.0

Minor Changes

  • #7501 83b8cdc Thanks @enisdenjo! - Polling interval option has been renamed to pollingInterval

    Breaking Changes

    import { UnifiedGraphManager } from '@graphql-mesh/fusion-runtime';
    
    const mngr = new UnifiedGraphManager({
    - polling: 10_000
    + pollingInterval: 10_000
    });
    

Patch Changes

0.6.0

Minor Changes

  • #7460 0c82de5 Thanks @enisdenjo! - Control subgraph execution batching in UnifiedGraphManager with batch option

Patch Changes

0.5.10

Patch Changes

  • Updated dependencies [a1bfc49]:
    • @graphql-mesh/types@0.99.7
    • @graphql-mesh/runtime@0.100.8
    • @graphql-mesh/utils@0.99.7
    • @graphql-mesh/transport-common@0.4.7

0.5.9

Patch Changes

0.5.8

Patch Changes

0.5.7

Patch Changes

0.5.6

Patch Changes

0.5.5

Patch Changes

  • #7343 597e790 Thanks @ardatan! - More verbose debug logs for HTTP fetch calls and subgraph requests

  • Updated dependencies [597e790, 597e790]:

    • @graphql-mesh/utils@0.99.4
    • @graphql-mesh/runtime@0.100.4
    • @graphql-mesh/types@0.99.4
    • @graphql-mesh/transport-common@0.4.4

0.5.4

Patch Changes

  • Updated dependencies [5e5dec5, 5e5dec5]:
    • @graphql-mesh/utils@0.99.3
    • @graphql-mesh/runtime@0.100.3
    • @graphql-mesh/types@0.99.3
    • @graphql-mesh/transport-common@0.4.3

0.5.3

Patch Changes

0.5.2

Patch Changes

0.5.1

Patch Changes

  • #7316 7800514 Thanks @enisdenjo! - dependencies updates:

  • #7253 2b8e52f Thanks @ardatan! - Fix the bug; When a non-nullable field is added through additionalTypeDefs in the compose config, then the gateway fails to resolve it even if a resolver defined in additionalResolvers;

    export const composeConfig = defineComposeConfig({
      subgraphs: [
        {
          sourceHandler: loadOpenAPISubgraph('Wiki', {
            source:
              'https://api.apis.guru/v2/specs/wikimedia.org/1.0.0/swagger.yaml',
            endpoint: 'https://wikimedia.org/api/rest_v1',
          }),
        },
      ],
      additionalTypeDefs: /* GraphQL */ `
        extend type pageview_project {
          banana: String
          apple: String!
        }
      `,
    });
    
    export const serveConfig = defineServeConfig({
      additionalResolvers: {
        pageview_project: {
          banana() {
            return '🍌';
          },
          apple() {
            return '🍎'; // This is ignored
          },
        },
      },
    });
    
  • #7266 26deb92 Thanks @ardatan! - Fix transformations on enum values

  • Updated dependencies [7800514, 7800514, 7800514, 7800514]:

    • @graphql-mesh/runtime@0.100.1
    • @graphql-mesh/transport-common@0.4.1
    • @graphql-mesh/types@0.99.1
    • @graphql-mesh/utils@0.99.1

0.5.0

Patch Changes

  • #7215 eefbfbe Thanks @ardatan! - Cleanup created transport executors per schema change Previously they were cleaned up only on server close, which could lead to memory leaks in case of schema changes.
  • Updated dependencies [69e6eb5, ededa2c, a8e3f00, a8e3f00, 69e6eb5, 69e6eb5]:
    • @graphql-mesh/transport-common@0.4.0
    • @graphql-mesh/utils@0.99.0
    • @graphql-mesh/runtime@0.100.0
    • @graphql-mesh/types@0.99.0

0.4.1

Patch Changes

0.4.0

Patch Changes

  • #7145 7544594 Thanks @Author, @User! - New Federation Composition Approach for the new Mesh v1 alpha; (If you are using Mesh v0 legacy, ignore this changelog)

    Now Mesh Compose produces a superset of Federated Supergraph.

    • Drop any options and implementation related to the old fusiongraph
      • The output is a valid supergraph that can be consumed by any Federation router. But if it is not Mesh Serve, the subgraph should still be served via Mesh Serve then consumed by that Federation router. If it is Mesh Serve, no additional server is needed because Mesh Serve already knows the additional directives etc of the transports
    • Compose the subgraphs using @theguild/federation-composition package
      • So benefit from the validation rules of Federation in Mesh Compose
    • Ability to consume existing federated subgraphs
      • Since the composition is now Federation, we can accept any federated subgraph
    • Implement Federation transform to transform any subgraph to a federated subgraph by adding Federation directives (v2 only) . This is on user's own because they add the directives manually. And for __resolveReference, we use @merge directive to mark a root field as an entity resolver for Federation
    • Use additional @source directive to consume transforms on the subgraph execution (field renames etc)
    • Use additional @resolveTo directive to consume additional stitched resolvers
    • Use additional @transport directive to choose and configure a specific transport for subgraphs
    • Handle unsupported additional directives with another set of additional directives on Query for example directives on unions, schema definitions, enum values etc and then @extraUnionDirective added with missing directives for unions then on the runtime these directives are added back to the union for the subgraph execution of the transports.

    Basically Mesh Compose uses Federation spec for composition, validation and runtime BUT the output is a superset with these additional directives imported via @composeDirective;

    • @merge (Taken from Stitching Directives) If a custom entity resolver is defined for a root field like below, the gateway will pick it up as an entity resolver;
    type Query {
       fooById(id: ID!): Foo @merge(keyField: 'id', keyArg: 'id', subgraph: Foo)
    }
    
    • @resolveTo (Taken from v0) This allows to delegate to a field in any subgraph just like Schema Extensions in old Schema Stitching approach;
        extend type Book {
    
            @resolveTo(
              sourceName: "authors"
              sourceTypeName: "Query"
              sourceFieldName: "authors"
              keyField: "authorId"
              keysArg: "ids"
            )
        }
    
    • @source Taken from Fusion This allows us to know how the original definition is in the subgraph. If this directive exists, the runtime applies the transforms from Schema Stitching during the subgraph execution. This directive can exist in arguments, fields, types etc.
    type Query {
     @source(type: "MyUser") # This means `User` is actually `MyUser` in the actual subgraph
    }
    
    type User @source(name: "MyUser") {
      id: ID
      name: String
    }
    
    • @transport Taken from Fusion This allows us to choose a specific transport (rest, mysql, graphql-ws, graphql-http etc) for the subgraph execution with some configuration. In the runtime, the gateway loads the transports and passes the subgraph schema with annotations if needed to get an executor to execute queries against that subgraph.
    schema
      @transport(
        subgraph: "API"
        kind: "rest"
        location: "http://0.0.0.0:<api_port>"
      ) {
      query: Query
      mutation: Mutation
      subscription: Subscription
    }
    
    • @extraSchemaDefinitionDirective By default, it is not possible to add directives from subgraph to the supergraph but it is possible to do the same thing on types or fields. So we add this directive to Query for the directives we want to add to the schema. Then the runtime picks those per subgraph to put the directives back to their original places;
    type Query @extraSchemaDefinitionDirective(
      directives: {transport: [{subgraph: "petstore", kind: "rest", location: "http://0.0.0.0:<petstore_port>/api/v3"}]}
    )  {
    
    • @extraEnumValueDirective and @extraTypeDirective Same for enum values and unions etc that are not supported by the composition library

    Thanks to these directives, subgraphs can be published individually to Hive for example then the supergraph stored there can be handled by Mesh Gateway since the composition is the same. All the additions etc are done on the subgraph level. For the Fed gateways except Mesh Serve, subgraphs can be served individually by Mesh Serve again while they are consumed by any gw like Apollo Router Shareable is enabled by default for non-federated subgraphs

    Documentation PR has details for users; https://github.com/ardatan/graphql-mesh/pull/7109

  • Updated dependencies [f985978, 7544594, 7544594]:

    • @graphql-mesh/utils@0.98.9
    • @graphql-mesh/transport-common@0.3.0
    • @graphql-mesh/runtime@0.99.11
    • @graphql-mesh/types@0.98.9

0.3.10

Patch Changes

  • Updated dependencies [6a99c52]:
    • @graphql-mesh/runtime@0.99.10

0.3.9

Patch Changes

0.3.8

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.98.7
    • @graphql-mesh/runtime@0.99.8
    • @graphql-mesh/utils@0.98.7
    • @graphql-mesh/transport-common@0.2.7

0.3.7

Patch Changes

0.3.6

Patch Changes

  • Updated dependencies [c4d2249]:
    • @graphql-mesh/utils@0.98.5
    • @graphql-mesh/runtime@0.99.6
    • @graphql-mesh/types@0.98.5
    • @graphql-mesh/transport-common@0.2.5

0.3.5

Patch Changes

  • fb59244 Thanks @ardatan! - Update GraphQL Tools packages

  • Updated dependencies [fb59244]:

    • @graphql-mesh/transport-common@0.2.4
    • @graphql-mesh/runtime@0.99.5
    • @graphql-mesh/types@0.98.4
    • @graphql-mesh/utils@0.98.4

0.3.4

Patch Changes

  • Updated dependencies [d9b5137]:
    • @graphql-mesh/runtime@0.99.4

0.3.3

Patch Changes

  • c47b2aa Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [c47b2aa]:

    • @graphql-mesh/transport-common@0.2.3
    • @graphql-mesh/runtime@0.99.3
    • @graphql-mesh/types@0.98.3
    • @graphql-mesh/utils@0.98.3

0.3.2

Patch Changes

  • 96dd11d Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [96dd11d]:

    • @graphql-mesh/transport-common@0.2.2
    • @graphql-mesh/runtime@0.99.2
    • @graphql-mesh/types@0.98.2
    • @graphql-mesh/utils@0.98.2

0.3.1

Patch Changes

  • Updated dependencies [6044b7f]:
    • @graphql-mesh/types@0.98.1
    • @graphql-mesh/runtime@0.99.1
    • @graphql-mesh/utils@0.98.1
    • @graphql-mesh/transport-common@0.2.1

0.3.0

Patch Changes

0.2.12

Patch Changes

  • Updated dependencies [afe0cc5]:
    • @graphql-mesh/runtime@0.98.8

0.2.11

Patch Changes

  • Updated dependencies [c008dda]:
    • @graphql-mesh/runtime@0.98.7

0.2.10

Patch Changes

0.2.9

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/runtime@0.98.6
    • @graphql-mesh/utils@0.97.5
    • @graphql-mesh/transport-common@0.1.5

0.2.8

Patch Changes

0.2.7

Patch Changes

0.2.6

Patch Changes

  • Updated dependencies [18e0d49]:
    • @graphql-mesh/runtime@0.98.5

0.2.5

Patch Changes

  • Updated dependencies [e2fb7ed, e2fb7ed]:
    • @graphql-mesh/utils@0.97.4
    • @graphql-mesh/runtime@0.98.4
    • @graphql-mesh/transport-common@0.1.4

0.2.4

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/runtime@0.98.3
    • @graphql-mesh/utils@0.97.3
    • @graphql-mesh/transport-common@0.1.3

0.2.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/runtime@0.98.2
    • @graphql-mesh/utils@0.97.2
    • @graphql-mesh/transport-common@0.1.2

0.2.2

Patch Changes

  • Updated dependencies [ccb80d8]:
    • @graphql-mesh/fusion-execution@0.0.2

0.2.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/runtime@0.98.1
    • @graphql-mesh/utils@0.97.1
    • @graphql-mesh/transport-common@0.1.1

0.2.0

Minor Changes

  • #6605 662a36a Thanks @enisdenjo! - Change executionRequest in onSubgraphExecute hook and use one transportKind argument instead of spreading it

Patch Changes

  • #6598 35b9cab Thanks @enisdenjo! - onSubgraphExecute hook can return nothing

  • Updated dependencies [92dce67, 70b05a2]:

    • @graphql-mesh/utils@0.97.0
    • @graphql-mesh/runtime@0.98.0
    • @graphql-mesh/transport-common@0.1.0

0.1.1

Patch Changes

0.1.0

Minor Changes

Patch Changes

0.0.2

Patch Changes

  • #6551 7c18a3f Thanks @enisdenjo! - No omnigraph transports and recommend graphql-mesh transports

  • Updated dependencies []:

    • @graphql-mesh/transport-common@0.0.2

0.0.1

Patch Changes

  • #6541 a7984e5 Thanks @ardatan! - New Fusion packages

  • Updated dependencies [a7984e5]:

    • @graphql-mesh/fusion-execution@0.0.1
    • @graphql-mesh/transport-common@0.0.1