Error: @nestjs/graphql tried to access graphql-tools, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

[andreialecu]

I'm submitting a...

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

@nestjs/graphql uses graphql-tools without listing it in its dependencies. It works in certain hoisting layouts because it hijacks it from apollo-server-core

This creates issues when using the package with Yarn's PnP resolution, and I assume also breaks the pnpm package manager.

Expected behavior

All imported packages should be listed in package.json.

What is the motivation / use case for changing the behavior?

It is a good practice to list all imported packages in package.json

Environment

Nest version: 7.7.0

[andreialecu]

Same issue with apollo-env:

Error: @nestjs/graphql tried to access apollo-env, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

graphql/lib/utils/transform-schema.util.ts

Line 29 in 61b01a5

import { mapValues } from 'apollo-env';

[kamilmysliwiec]

Fixed