- How do I install stayallive/lighthouse-graphql-hive in a Laravel app?
- Install it with Composer as stayallive/lighthouse-graphql-hive, then publish its config using Laravel's vendor:publish command. Set the Hive token and endpoint environment variables and ensure the service provider is registered, which Laravel package discovery typically handles. You must already have a GraphQL Hive project and target because telemetry is only meaningful against a published schema.
- Does this package work with Laravel 10, 11, and 12 and current Lighthouse versions?
- It is built for Laravel applications using Lighthouse, but the provided technical assessment says compatibility with specific Laravel 10, 11, and 12 releases and current Lighthouse majors must be verified explicitly. Check the package composer.json constraints and CI matrix before adoption. Pin the version and add a CI check that boots the app with the service provider registered to catch framework drift early.
- Can I use lighthouse-graphql-hive without Laravel Lighthouse?
- No. This package is a thin instrumentation adapter that connects Lighthouse's middleware and event pipeline to GraphQL Hive. If your GraphQL server is not Laravel Lighthouse, use GraphQL Hive's generic GraphQL clients or HTTP reporting protocol instead.
- Does it report GraphQL operations inline on the request or buffer and queue them?
- The package hooks into Lighthouse's middleware and event pipeline to capture operation names, timing, errors, and optionally traces, then ships them to Hive's usage-reporting endpoint. The provided assessment does not confirm whether delivery is inline or buffered and queued, or whether failures fail open. Read the source and test with an unreachable Hive endpoint before relying on it in production.
- Does lighthouse-graphql-hive support self-hosted GraphQL Hive?
- The integration uses configurable Hive token and endpoint values, which suggests it can point at a self-hosted Hive instance. However, you must verify that the usage-reporting protocol version expected by the package matches your self-hosted Hive server. Confirm this in the config and source before committing to self-hosting.
- Does this package handle schema publishing and schema checks or only usage monitoring?
- The package description mentions reporting schema usage, validating schemas, and managing schema publishing, but the technical assessment flags feature scope as ambiguous. Confirm in the source and README whether it covers usage reporting only or also schema publish and schema checks. Many teams still use the Hive CLI or CI workflows for schema publishing and checks.
- Are GraphQL operation variables and error bodies sent to Hive, and can I redact them?
- The assessment warns that operation reporting can capture variables and error payloads, so redaction and PII handling must be designed and verified rather than assumed. Check the package configuration and source for what is transmitted and whether redaction hooks exist. Gate reporting by environment and avoid sending sensitive variables from production or developer machines.
- How should I test and roll out GraphQL Hive monitoring with this Laravel package?
- Enable reporting in staging and production but disable it locally to avoid noise and accidental data egress. Add a CI check that boots Laravel with the provider registered and sends a sample GraphQL operation to a mock or disabled Hive endpoint to confirm the integration fails open. Then tune sampling per environment after verifying which sampling controls the package supports.
- What are alternatives to stayallive/lighthouse-graphql-hive?
- If you are not using Laravel Lighthouse, use GraphQL Hive's generic GraphQL clients or HTTP reporting protocol. If you are on Lighthouse but want to avoid this package, implement your own middleware against Hive's usage-reporting endpoint. The practical fallback if the package is abandoned is Hive's generic reporting protocol.
- Is lighthouse-graphql-hive actively maintained and safe to adopt?
- The adoption signal is thin at roughly 22 stars, and the assessment flags a future release date anomaly, so treat maintenance cadence as unverified until you check release history and commit activity. Review issue response times and explicitly confirm Laravel, Lighthouse, PHP, and Hive protocol compatibility. Pin the package version and keep a fallback to Hive's generic reporting protocol.