* Add BadUserInputError and TransientError as extensions of ApolloError

* remove TransientError

* update test so that properties end up under `error.extensions.exception`

* update documentation to talk about BadUserInputError

* check for properties after formatApolloErrors has been called

* fixed highlighted lines for docs

* export BadUserInputError from `apollo-server`

* fixed highlighted lines for docs

* export BadUserInputError from `apollo-server`

* update changelog

See https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-7.html

* feat: ApolloServer is created and exported by all variants

* docs: add initial docs around exporting ApolloServer

* feat: export gql from integrations

* docs: change apollo-server examples to use express with registerServer

* server: remove registerExpressServer

* core, docs: comment functions, fix api reference, context creation more like middleware args

* docs: fix integrationed typo

We recommend the use of apollo-engine-reporting and the other built-in features
of AS 2.0 rather than engineProxy. You can still use the apollo-engine npm
module manually with AS 2.0, or stay on AS 1.0.

Previously, we were planning to offer two kinds of APIs in "Apollo Server 2":
middleware functions just like in 1.0, and the new ApolloServer class.  We have
not yet implemented ApolloServer for all of our supported web frameworks, so
this meant that the 2.0 version of modules such as apollo-server-koa (which does
not yet have an ApolloServer class) offered very little benefits over
[email protected] (as most of the benefits of 2.0 come from ApolloServer).

This is confusing. We are going to improve the current registerServer API so
that there's no real benefit to using a separately-exported middleware directly
rather than creating an ApolloServer and applying it to your web framework. So
the AS 2.0 API will just be ApolloServer.  This means it doesn't make sense for
us to publish 2.x versions of the packages that don't yet support this API.

So this commit removes support for the following web frameworks: Adonis, Azure
Functions, Koa, Lambda, Micro, and Restify. (We leave in place Express, Hapi,
and Cloudflare workers.)

This isn't because we don't like these frameworks and don't want them to work
with Apollo Server 2.0!  We would love to see each package resurrected and an
ApolloServer implementation built, either during this current 2.x beta phase or
after the official 2.0 release. Deleting these packages for now makes it more
clear which frameworks support 2.0 and which don't, rather than existing in a
state where apollo-server-express@2 has ApolloServer and apollo-server-koa@2
does not.

ApolloServer builds in graphql-playground rather than graphiql, so we no longer
provide middleware for serving GraphiQL.

If this turns out to be an unpopular choice, we can always add support for
graphiql instead of graphql-playground back in later.

We prefer graphql-playground because it allows you to enter HTTP request
headers, view query history, and explicitly supports [email protected].

We are going to tweak registerServer until there is no reason to prefer a
non-ApolloServer-associated middleware function over using it.

Fix some connect bugs.

Since f0f75b1, it seems important to
restore the reasoning for the usage of `yarn` to avoid confusion in the
future.  This comment was originally removed in 301e144.

This reverts the comment from that commit and further improves the clarity.

Ref: 301e144d#r29319011

…r express

Emacs tide mode seems to require
this (ananthakumaran/tide#238 is supposed to have fixed
it but it didn't work?)

also export graphql-tools and graphql-subscriptions from apollo-server-core

* Enable declarationMap in tsconfig.json

See http://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-9.html

* Add apollo-server-caching package and improve typings

* Remove superfluous test steps

* Add .npmignore to apollo-server-caching

* Add apollo-server-env and apollo-datasource-rest packages

* Fix broken imports

* Use prepublish instead of prepare

* cache is now passed to data sources from ApolloServer constructor

* fix Object.values to use the object passed in rather than this

* add initial datasource test

* docs: initial data source documentation

* docs: initial data source documentation

* compiles and documentation now highlights code in data-sources.md

* Some changes to the data source docs

* add doc for subscriptions

* apply few changes to the readme

* apply few changes to the readme

* add more informations in case req is null

* changed last sentence

* apply comments

* typo

* remove idea folder

* fix indentation

* fix typo

* subscriptions with middleware

* subscriptions with middleware

* subscriptions with middleware

This was lost in 639b104.

This was still linked from the v2 getting started page.  While it will
eventually link to the "Deployment" guide index page where we'll offer
guides for other deployment options, that content is not written.

For now, we'll offer those getting statred to deploy with Heroku, which is
written!

Ref: https://twitter.com/jevakallio/status/1007915638919192577
cc (and thanks) to @jevakallio for pointing this out.

Change  to  in new pattern of using apollo server 2

the url is incorrect: example.com//.well-known/apollo/server-health

remove extra '/' from docs

[DOCS] added missing 'new' keyword at error handling examples

* Refactored caching connectors into their own packages
- apollo-server-caching (exports interface for KeyValueCache)
- apollo-server-caching-memcached
- apollo-server-caching-redis
One issue now is that there is duplication of mocks and test code in each of the packages. It would be better if we had centralized integration tests for all cache connectors, community contributed or otherwise.

* export test suite for cache connectors from `apollo-server-caching`

* fixed tsconfig.json

* added @types

This removes an unnecessary instruction to install `apollo-server` when using the middleware option with Apollo Server 2.0.

While this was necessary in earlier versions of the Apollo Server 2.0 alpha and beta releases, it is no longer needed.

reason: "bad" and "error" are redundant

…caches

Not sure if Renovate will catch this due to a misconfiguration on my part.

…anches.

* add string input to gql tag

* remove esModuleInterop, tested locally

* change IMPORT_FUNCTION to something real

* fix the rest of the tests

Because apollo-server-core depends on apollo-datasource-rest, we need to extract errors into their own package to avoid a circular dependency.

We now support custom extensions, which have a much nicer API.

* move uploads into server constructor

* remove enhanceSchema

* address feedback

Smaller default uncompressedReportSizeTarget