Weave Code
Hasura Bundle Laravel Package
hasura-extra/hasura-bundle
A Symfony bundle for integrating the Hasura GraphQL engine into PHP applications. It provides configuration, service wiring, and convenience tooling so you can connect to Hasura, manage settings, and query its APIs more easily. Simplify setup and streamline GraphQL workflows from your Symfony projec...
Hasura Bundle brings the hasura-extra PHP toolkit into Symfony, making it easier to configure and use Hasura GraphQL services in your application. It wires Hasura clients into the Symfony container and supports common Hasura workflows through familiar bundle configuration.
- Symfony DI integration for Hasura client services
- Configurable Hasura endpoint and request headers
- Query and mutation execution from PHP
- Schema and metadata tooling support where available
- Lightweight setup for Hasura-backed Symfony apps
Frequently asked questions about Hasura Bundle
- Is hasura-extra/hasura-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. Its namespace, its dependency-injection service registration, and the hasura-extra project family are all Symfony-first, and there is no Laravel PackageManifest auto-discovery path. A separate hasura-extra/laravel sibling exists, but it inherits the same abandonment profile.
- How do I install hasura-extra/hasura-bundle in Laravel?
- Practically, you should not. There is no auto-discovery, so the bundle's services and config tree would need manual re-registration or bypassing, and Composer may fail outright because the bundle pulls symfony/http-kernel, symfony/dependency-injection, and symfony/config, which Laravel pins to its own versions. A one- to two-day install spike is the only way to know for sure, and it should happen before any design work.
- Why is hasura-extra/hasura-bundle deprecated?
- The maintainers marked it deprecated and archived the repository, pointing users to hasura-extra/bundle instead. The last release was 2021-10-27, with no CVE response channel, no PHP minor-version fixes, and effectively no adoption (six stars, zero dependents). It is also a 2021-era adapter for Hasura v2-era contracts while Hasura has moved toward v3/DDN.
- What should I use instead of hasura-extra/hasura-bundle?
- The direct replacement named by the maintainers is hasura-extra/bundle. For Laravel specifically, the bundle's responsibilities map onto framework primitives: controllers with FormRequest validation for actions, queued jobs for event triggers, middleware for webhook secret verification, and the Http facade for Hasura metadata calls. Reading this bundle as a specification and writing a thin internal adapter is usually cheaper than adopting an unmaintained dependency. Evaluate hasura-extra/laravel only after confirming its maintenance status.
- Does hasura-extra/hasura-bundle support Laravel 10 or 11 and PHP 8.1+?
- That is unverified. The release line is 2021-era and PHP 8.1+/8.2+ compatibility is not documented; the most likely blockers are Symfony component version collisions with Laravel's own pinned dependencies, plus PHP deprecation noise. Pin the runtime explicitly and run a matrix against each Laravel version in your support window before committing to anything.
- What does hasura-extra/hasura-bundle actually handle for Hasura actions and event triggers?
- It standardizes the Hasura HTTP contracts that are genuinely fiddly to hand-roll. That includes the action request envelope (action.name, input, session_variables, request_query), the response and error shape Hasura expects (extensions.code, extensions.path), event-trigger payload parsing, and client wrappers for Hasura's metadata API. The glue is roughly 150 to 300 lines per integration, which is worth understanding even if you never install the bundle.
- Is hasura-extra/hasura-bundle maintained and safe for production use?
- No. The repository is archived with a single maintainer, six stars, zero dependents, and a last release dated 2021-10-27. There is no security disclosure channel and no CVE response, so a Hasura contract change or a PHP minor-version issue would be yours to fix. Treat it as high lifecycle risk rather than a code-quality problem.
- How do I handle Hasura action errors and event triggers natively in Laravel?
- Map each responsibility onto a Laravel primitive: action handlers become controllers with FormRequest validation, event triggers become queued jobs, webhook secret verification becomes middleware, and Hasura client calls go through the Http facade. On the response side, build a small error-response builder that emits extensions.code and extensions.path exactly as Hasura expects, plus a DTO for the action request envelope and a parser for event payloads. That gives you the same contract coverage without an unmaintained Symfony dependency.
- Does hasura-extra/hasura-bundle work with Hasura v2 and Hasura v3/DDN?
- The bundle was built for Hasura v2-era Actions and Event Triggers contracts. Hasura v3/DDN reshapes how custom business logic is wired, so a 2021 adapter locks you to a model Hasura itself has moved past. Confirm which Hasura version you are targeting before evaluating any of this.
- Should I fork hasura-extra/hasura-bundle for a Laravel project, and how would I test it?
- Fork only if concept transfer is genuinely not enough; for most teams a thin internal package is cheaper. If you do fork, move it under your own vendor namespace, pin the PHP constraint, strip the Symfony kernel coupling, add CI across your supported Laravel versions, and document the decision in an ADR. Test it by building fixture payloads for the action request envelope and error shape and asserting your adapter emits the exact JSON Hasura expects.
Weaver
How can I help you explore Laravel packages today?