graphql-mesh

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [f16df1f9b]
  • @graphql-mesh/[email protected]

Patch Changes

• f16df1f9b: Missing scalar 'File' error has been fixed when there is a stream request in the gRPC protobuf schema

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• 0401c7617: Improvements on string interpolation ({env.sth} or {context.headers.sth}) for different environments

  As we mention in most of our docs, we usually expect a key-value header object in the context.
  But Fetch-like environments don't have this kind of object but instead Headers object which is a kind Map.
  Now Mesh can detect this and automatically convert it to the key-value object especially for Yoga users.

  Also Mesh now handles env in a better way for non-Node environments;

  Consider import.meta.env as env if available, else take globalThis as env.

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[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 [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• 0401c7617: Fix: Resolve customFetch properly and write the import statement properly in the artifacts

  If given customFetch path is relative, it wasn't reflected properly in the generated artifacts so artifacts were failing. Now it is resolved correctly based on the given working directory(baseDir).

• Updated dependencies [66f5d0189]

• Updated dependencies [0401c7617]

  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[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 [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[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 [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @omnigraph/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• 0401c7617: Improvements on string interpolation ({env.sth} or {context.headers.sth}) for different environments

  As we mention in most of our docs, we usually expect a key-value header object in the context.
  But Fetch-like environments don't have this kind of object but instead Headers object which is a kind Map.
  Now Mesh can detect this and automatically convert it to the key-value object especially for Yoga users.

  Also Mesh now handles env in a better way for non-Node environments;

  Consider import.meta.env as env if available, else take globalThis as env.

Patch Changes

• Updated dependencies [66f5d0189]
• Updated dependencies [0401c7617]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• 0401c7617: Improvements on string interpolation ({env.sth} or {context.headers.sth}) for different environments

  As we mention in most of our docs, we usually expect a key-value header object in the context.
  But Fetch-like environments don't have this kind of object but instead Headers object which is a kind Map.
  Now Mesh can detect this and automatically convert it to the key-value object especially for Yoga users.

  Also Mesh now handles env in a better way for non-Node environments;

  Consider import.meta.env as env if available, else take globalThis as env.