apollo-server-lambda: make main method async

Inline graphqlLambda
apollographql · Mar 9, 2021 · e53333b · e53333b
1 parent 5a72050
commit e53333b
Show file tree

Hide file tree

Showing 3 changed files with 247 additions and 248 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -12,6 +12,7 @@ The version headers in this history reflect the versions of Apollo Server itself
 > The changes noted within this `vNEXT` section have not been released yet.  New PRs and commits which introduce changes should include an entry in this `vNEXT` section as part of their development.  With few exceptions, the format of the entry should follow convention (i.e., prefix with package name, use markdown `backtick formatting` for package names and code, suffix with a link to the change-set à la `[PR #YYY](https://link/pull/YYY)`, etc.).  When a release is being prepared, a new header will be (manually) created below and the appropriate changes within that release will be moved into the new section.
 
 - `apollo-server-core`: The `SIGINT` and `SIGTERM` signal handlers installed by default (when not disabled by `stopOnTerminationSignals: false`) now stay active (preventing process termination) while the server shuts down, instead of letting a second signal terminate the process. The handlers still re-signal the process after `this.stop()` concludes. Also, if `this.stop()` throws, the signal handlers will now log and exit 1 instead of throwing an uncaught exception. [Issue #4931](https://github.com/apollographql/apollo-server/issues/4931)
+- `apollo-server-lambda`: Support the nodejs14 runtime by changing the handler to be an [async handler](https://docs.aws.amazon.com/lambda/latest/dg/nodejs-handler.html#nodejs-handler-async). (For backwards compatibility, if the handler receives a callback, it still acts like a non-async handler.) [Issue #1989](https://github.com/apollographql/apollo-server/issues/1989) [PR #5004](https://github.com/apollographql/apollo-server/pull/5004)
 
 ## v2.21.1