Import d.ts from @apollo/federation and @apollo/gateway instead of ts

[shian15810]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Currently, the ts files from @apollo/federation and @apollo/gateway are being imported directly, hence any stricter configuration to tsconfig.json on the consumer level is being enforced on these ts files from @apollo/federation and @apollo/gateway.

For example, I have importsNotUsedAsValues as error in my local tsconfig.json, and even with skipLibCheck as true, tsc still throw this error:

node_modules/@apollo/gateway/src/datasources/types.ts:1:1 - error TS1371: This import is never used as a value and must use 'import type' because 'importsNotUsedAsValues' is set to 'error'.

1 import { GraphQLResponse, GraphQLRequestContext } from 'apollo-server-types';
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[8:31:55 PM] Found 1 error. Watching for file changes.

What is the new behavior?

With the changes, tsc will resolve d.ts files in dist instead of ts files in src. Hence any stricter configuration made in tsconfig.json is not being applied on these ts files anymore.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[kamilmysliwiec]

LGTM

[shian15810]

Thanks. Is it possible to have a new release?