apollo-server
apollo-server copied to clipboard
🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
When installing `@apollo/server` v4 in a TS project using `"module": "nodenext"`, TS throws a bunch of errors about how Apollo Server's imports need to use extensions. Specifically, we omitted extensions...
Lots of errors like this: ``` node_modules/@apollo/server/dist/esm/externalTypes/plugins.d.ts:6:344 - error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './requestPipeline.js'?...
In order to make usage reporting have better performance and less potential PII leakage by default, we should change the default usage reporting to send even less information by default....
This is an attempt at addressing #6423. However, it sure seems like `typesVersions` is kinda janky and doesn't work as well as we'd like. One particular thing I've found is...
Functionality is the same. This PR updates `apollo-server-errors` to have strict types rather than magic strings and then exports those types for use in other applications. We need these types...
I'm writing an Apollo Server plugin that validates a presence of a certain HTTP header. It looks like this: ```ts import { ApolloServerPlugin } from 'apollo-server-plugin-base'; import { OperationDefinitionNode }...
Fixes https://github.com/apollographql/apollo-server/issues/6603 All GET requests sent with RESTDatasource go through a memoization cache but there is currently no option to disable that. This change adds a new class property `requestCacheEnabled`...
Draft pull request to go along side #6635 where changes have be outlined there. In summary: 1. Update dependencies for Fastify v4 while still supporting v3. 2. Changed connecting API...
We'd like Apollo Server 4.0 to support incremental delivery (`@defer`/`@stream`) if combined with a version of `graphql-js` that supports it. We expect this may impact the plugin API (as it...