Weave Code
Laravel Graphql Playground Laravel Package
mll-lab/laravel-graphql-playground
Adds the GraphQL Playground IDE to your Laravel app, giving you an in-browser interface to explore schemas, write queries, and test your GraphQL API. Integrates smoothly with Laravel GraphQL servers such as Lighthouse and is quick to install and configure.
This project is deprecated in favor of https://github.com/mll-lab/laravel-graphiql.
Frequently asked questions about Laravel Graphql Playground
- Is mll-lab/laravel-graphql-playground deprecated?
- Yes. The project is deprecated in favor of mll-lab/laravel-graphiql, and the upstream GraphQL Playground IDE itself is end-of-life in favor of GraphiQL 2. The repository is archived and has had no releases since February 2022, so it receives no security or compatibility fixes.
- Which Laravel and PHP versions does laravel-graphql-playground support?
- The last release predates Laravel 9 general availability, so its Composer constraints were not written for Laravel 10 or 11 or PHP 8.2+. You should audit the package's composer.json against your pinned Laravel and PHP versions before attempting an install. In practice, modern Laravel applications are likely to hit dependency resolution conflicts.
- How do I install laravel-graphql-playground?
- Historically you installed it as a dev dependency with composer require --dev mll-lab/laravel-graphql-playground. Laravel auto-discovery registers the service provider, and you can publish the config with php artisan vendor:publish. The IDE is then served at the configured route against your GraphQL endpoint. Because the package is deprecated, new installs are not recommended.
- How do I configure the GraphQL endpoint for laravel-graphql-playground?
- Publish config/graphql-playground.php using vendor:publish, then set the endpoint to your GraphQL server path. With Lighthouse, that is typically /graphql by default. You can also adjust route and middleware settings in that config file. Confirm the published file has not drifted if you later migrate.
- Is it safe to use GraphQL Playground in production?
- No, not by default. The route can execute arbitrary GraphQL queries with introspection, which creates schema-disclosure and query-abuse risk if it is reachable in production. The package does not environment-gate the route or add auth middleware for you. Keep it local-only or behind authentication and authorization.
- How do I protect the playground route with middleware?
- Configure the route middleware in the published config file so the IDE is gated by Laravel auth or another access-control middleware. Also ensure the route is only registered in local or non-production environments. Because the package is deprecated, prefer implementing this in your own route or in the successor package. Do not rely on the package to secure the endpoint for you.
- What should I use instead of laravel-graphql-playground?
- Use mll-lab/laravel-graphiql, the maintainer's direct successor with the same provider, config-publish, and route pattern. Alternatively, drop the dependency and serve GraphiQL or Apollo Sandbox from a single Blade view behind an environment check and auth middleware. The second option removes a third-party from your supply chain and makes the CDN version decision explicit.
- How do I migrate from laravel-graphql-playground to laravel-graphiql?
- Treat it as a rename-plus-config-diff. Replace the Composer requirement, publish the new config, and port endpoint and middleware settings. Audit any hand-edited config drift and confirm the GraphQL endpoint path and auth headers. Then remove the old provider and route.
- Does laravel-graphql-playground work without Lighthouse?
- It can, because it is a thin wrapper that points an IDE at a configured GraphQL endpoint. However, it is clearly intended to pair with Lighthouse, the maintainer's GraphQL server, and you gain nothing over a hand-rolled route without that convention. If you are not on Lighthouse, consider a simple custom view instead.
- Why does laravel-graphql-playground load assets from a CDN?
- The IDE is loaded from a CDN by default, which means availability and version of the GraphQL Playground assets are outside your control. That creates a silent single point of failure for a tool teams come to depend on. If you keep an IDE, consider vendoring assets or using a maintained alternative.
Weaver
How can I help you explore Laravel packages today?