#Conflicting peer dependencies. Deprecation of deprecation of @apollo/server-plugin-landing-page-grap

1 messages · Page 1 of 1 (latest)

azure lark
#

Hello, I just updated my nest packages and faced an issue with peer deps . As I can see @nestjs/apollo uses already deprecated @apollo/server-plugin-landing-page-graphql-playground package. I also found this issue https://github.com/nestjs/nest/issues/15890 but it unfortunately it got closed without proper solution. Are there any workaround?

Thanks in advance 🙇🏻‍♂️

GitHub

Is there an existing issue for this? I have searched the existing issues Current behavior Below one was while npm i : npm warn While resolving: @apollo/server-plugin-landing-page-graphql-playground...

azure lark
#

ok, seems like I solved the error just by installing @apollo/server

Can be considered as solved I guess

grim prairie
#

Hmm, for me it's not an error but a warning since I installed @apollo/server v5 :

npm warn Could not resolve dependency:
npm warn peer @apollo/server@"^4.0.0" from @apollo/[email protected]
npm warn node_modules/@apollo/server-plugin-landing-page-graphql-playground
npm warn   @apollo/server-plugin-landing-page-graphql-playground@"4.0.1" from @nestjs/[email protected]
npm warn   node_modules/@nestjs/apollo
echo thicket
#

You should simply remove the plugin, as it is no longer needed in Apollo Server v5. Use the built-in sandbox.

grim prairie
echo thicket
# grim prairie We don't have it at all, but it seems it's a peer dep of @nestjs/[email protected]

It's actually a dependency. But, if you just install the apollo package, it becomes the warning, which can be ignored. Not sure why Kamil kept it in the Apollo package. It's definitely not needed. I've created an issue. We'll see if it get handled.
https://github.com/nestjs/graphql/issues/3804

GitHub

Is there an existing issue for this? I have searched the existing issues Current behavior Hi, @apollo/server-plugin-landing-page-graphql-playground should be removed as a dependency from the apollo...

echo thicket
#

Looks like the answer is now: Please be patient until the next major version. Then this issue will be fixed.