A set of utils for faster development of GraphQL tools
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)
graphql-hive0512be3]:4e33933]:278618a]:2318393]:#620 d72209a Thanks @renovate! - dependencies updates:
@graphql-tools/utils@^10.8.1 ↗︎ (from ^10.7.0, in dependencies)Updated dependencies [d72209a]:
9144222]:18682e6]:#373 e606975 Thanks @ardatan! - dependencies updates:
@graphql-tools/utils@^10.7.0 ↗︎ (from ^10.6.2, in dependencies)Updated dependencies [e606975]:
23b8987]:#291 34d1224 Thanks @ardatan! - dependencies updates:
tslib@^2.8.1 ↗︎ (from ^2.4.0, in dependencies)Updated dependencies [34d1224]:
#269 cdca511 Thanks @ardatan! - dependencies updates:
@graphql-tools/utils@^10.6.2 ↗︎ (from ^10.6.0, in dependencies)Updated dependencies [7df2215, cdca511]:
9ce705c]:7ca0ff3]:2e0add3]:#164 310613d Thanks @ardatan! - dependencies updates:
@graphql-tools/utils@^10.6.0 ↗︎ (from ^10.5.6, in dependencies)Updated dependencies [310613d]:
f32cb2a]:73c621d]:342e044]:e9906eb]:da1de08]:f470f49]:180f3f0]:8effad4]:8a16b01]:4cdb462]:7e2938d]:cf2ce5e]:ca57eae
Thanks @ardatan! - Support multiple entrypoints with
@merge(keyField)
type User {
id: ID!
name: String!
}
type Query {
userById(id: ID!): User @merge(keyField: "id")
userByName(name: String!): User @merge(keyField: "name")
}
27b6f49
Thanks @asodeur! - Adding the ability to return non-scalar types
from computed fields. Computed fields can now return object types (local or stitched), interfaces,
unions, or enums.83c0af0
Thanks @enisdenjo! - dependencies updates:@graphql-tools/delegate@^10.0.3 ↗︎
(from ^10.0.0, in dependencies)@graphql-tools/utils@^10.0.13 ↗︎
(from ^10.0.0, in dependencies)83c0af0,
83c0af0]:8fba6cc1,
944a68e8,
944a68e8]:1c95368a
Thanks @ardatan! - Use ranged versions for dependencies
Updated dependencies []:
f26392a6]:492220cb]:30bd4d0c]:b09ea282,
b5c8f640]:a94217e9,
62d074be]:772b948a]:a4d36fcc,
e3ec35ed]:13177794]:904fe770,
904fe770]:13c24883,
b5e6459f]:7411a5e7]:c0639dd0]:d83b1960]:80836fa7,
8f6d3efc,
80836fa7,
80836fa7,
80836fa7]:f7daf777]:df5848b8,
df5848b8,
df5848b8,
df5848b8]:0402894d]:00c4a1a4]:43c736bd]:71cb4fae,
403ed450]:4fe3d9c0]:#4640
27bdc237
Thanks @ardatan! - dependencies updates:
@graphql-tools/delegate@9.0.3 ↗︎
(was 9.0.2, in dependencies)0555a972]:29ee7542]:2609d71f]:#4624
e3167edc
Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with
moduleResolution node16 or nodenext
Updated dependencies
[e3167edc,
d8dc67aa]:
74581cf3: fix(getDirectives): preserve order around repeatable directives
BREAKING CHANGE: getDirectives now always return an array of individual DirectiveAnnotation
objects consisting of name and args properties.
New useful function getDirective returns an array of objects representing any args for each use
of a single directive (returning the empty object {} when a directive is used without
arguments).
Note: The getDirective function returns an array even when the specified directive is
non-repeatable. This is because one use of this function is to throw an error if more than one
directive annotation is used for a non repeatable directive!
When specifying directives in extensions, one can use either the old or new format.
24926654: Deprecates the MergeTypeConfig.computedFields setting (with backwards-compatible
warning) in favor of new computed field configuration written as:
merge: {
MyType: {
fields: {
myComputedField: {
selectionSet: '{ weight }',
computed: true,
}
}
}
}
A field-level selectionSet specifies field dependencies while the computed setting structures
the field in a way that assures it is always selected with this data provided. The selectionSet
is intentionally generic to support possible future uses. This new pattern organizes all
field-level configuration (including canonical) into a single structure.
6e50d9fc: enhance(stitching-directives): use keyField
When using simple keys, i.e. when using the keyField argument to @merge, the keyField can be
added implicitly to the types's key. In most cases, therefore, @key should not be required at
all.
Updated dependencies [6e50d9fc]
c3996f60: fix(stitchingDirectives): fix name clash
export all stitching directives as allDirectives instead of
stitchingDirectives as the main package function isstitchingDirectives`
Updated dependencies [c3996f60]