fix(fastify): use scoped modules

[SimenB]

The official plugins of fastify are now scoped, and the old names are deprecated. There should be no other breaking changes.

[netlify]

👷 Deploy request for apollo-server-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	55219f5

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 55219f5:

Sandbox	Source
Apollo Server Typescript	Configuration
Apollo Server	Configuration

[glasser]

@SimenB Just to check: are the new packages fully backwards compatible with the old ones (eg, can you use the accepts and cors middlewares from the new packages with the same versions of Fastify as before?), or will users upgrading to a newer version of apollo-server-fastify need to upgrade Fastify as well?

(For what it's worth, we will be solving this problem in Apollo Server 4 by not trying to magically wrap these middleware in our own middleware and trusting that (with clearly documented examples) folks can use these middleware directly. We will also be decoupling the apollo-server-fastify release process from the Apollo Server core release process by providing a stable API between ApolloServer and web framework integrations and allowing active users of web frameworks like Fastify to maintain the integration with their expertise.)

[SimenB]

Yeah, only breaking change is the rename 🙂

[glasser]

Great. Mind resolving the package-lock.json conflict? Rebasing should clear up the spell-check failure too.

[SimenB]

@glasser done 🙂

[glasser]

Thanks! I'll put this out in [email protected] today.