Packages

@apollo/server-plugin-landing-page-graphql-playground

4.0.1 · 26 May 2023MIT540.1k / weekRepositoryHomepagenpmAtom feed

Deprecated by its maintainers: The use of GraphQL Playground in Apollo Server was supported in previous versions, but this is no longer the case as of December 31, 2022. This package exists for v4 migration purposes only. We do not intend to resolve security issues or other bugs with this package if they arise, so please migrate away from this to [Apollo Server's default Explorer](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages) as soon as possible.What to use instead

What to use instead of @apollo/server-plugin-landing-page-graphql-playground

Its maintainers have deprecated it: no fix is coming, so the next advisory stays open. Here is what they and the community point to instead.

Deprecated by its maintainers

The use of GraphQL Playground in Apollo Server was supported in previous versions, but this is no longer the case as of December 31, 2022. This package exists for v4 migration purposes only. We do not intend to resolve security issues or other bugs with this package if they arise, so please migrate away from this to [Apollo Server's default Explorer](apollographql.com/docs/apollo-server/api/plugin…) as soon as possible.

The message names no replacement, and the e18e list has no entry for @apollo/server-plugin-landing-page-graphql-playground yet.

Before you switch

  1. 1

    Check what else depends on it

    Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.

  2. 2

    Read the replacement's peers and releases

    A native API or a few lines of code need no release notes, but check the Node version your project runs on.

  3. 3

    Know when it ships

    Follow the new package on Inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.