graphql-js
graphql-js copied to clipboard
graphql
A reference implementation of GraphQL for JavaScript
Adds a production performance guide for the performance series, focused on improving GraphQL server performance in production environments. Covers: - Identifying bottlenecks - Batch database operations - Caching strategies -...
Adds guide for production monitoring/observability. Covers: - Integration examples w/ explanations and best practices - Structured logging - Metrics - Query complexity tracking - Sampling
just tightening the loop!
via using a new generic type parameter with this pattern: ```ts export interface ExecutionResult< TData = ObjMap, TExtensions = ObjMap, TError extends GraphQLError | GraphQLFormattedError = GraphQLError, > { errors?:...
Per [the spec](https://spec.graphql.org/draft/#sec-Extensions): > The "extensions" entry in an [execution result](https://spec.graphql.org/draft/#execution-result) or [request error result](https://spec.graphql.org/draft/#request-error-result), if set, must have a map as its value. This entry is reserved for implementers...
First guide in the new GraphQL production guide series, focusing specifically on build optimization for production deployments. Content covers: - Environment variable configuration for GraphQL.js optimization - Dead code elimination...
When resolving an output value through `Int` scalar, `NaN` causes an error to be thrown: > Int cannot represent non-integer value: NaN ```js const schema = makeExecutableSchema({ typeDefs: /* GraphQL...
The `@depreacted` marks might be heavy-handed. I am completely fine with reversing those. For environments that don't have `Error.cause` (ES2021) `@deprecated` might be annoying to deal with, since they don't...
ECMAScript has standardized around `new Error(message, { cause })` pattern. We have the `originalError` option. I'd hope we could alias and deprecate `originalError` in favor of `cause` to bring uniformity....
Take the following: ```ts declare const chunk: FormattedIncrementalResult; if ("items" in chunk) { const { items } = chunk; // TypeScript error items.slice(0); } ``` When providing a generic to...
