Weave Code
Flightstats Bundle Laravel Package
spiicy/flightstats-bundle
A PHP bundle for integrating the FlightStats API, with configurable clients and helpers to retrieve flight status, schedules, airport, airline, and related aviation data in your application.
At a glance
Frequently asked questions about Flightstats Bundle
- Is spiicy/flightstats-bundle a Laravel package?
- No, it is a Symfony bundle rather than a Laravel package. It plugs into Symfony through a Bundle subclass, DI extension, and Configuration tree, which Laravel's service container does not resolve. In Laravel you would need to vendor or fork the underlying client code and discard the Symfony scaffolding.
- How do I install spiicy/flightstats-bundle in a Laravel app?
- A direct Composer install is likely to conflict because the bundle targets old Symfony, PHP, and Guzzle constraints. Even if it installs, Laravel will not auto-discover or boot the Symfony bundle. The practical route is to copy the service classes into app/Services/FlightStats or a private path repository and bind them in a Laravel service provider.
- Which Laravel and PHP versions are supported?
- The bundle is not designed around Laravel version support. The assessment points to Symfony 2/3-era constraints, PHP ^5.6/^7.0, and older Guzzle, which makes direct use on Laravel 10 or 11 with PHP 8.2+ unlikely without a fork. Verify the Composer constraints before planning any integration.
- How do I configure FlightStats API credentials?
- In the original bundle, credentials and endpoint settings are configured through Symfony bundle configuration. In Laravel, move those values into config/services.php or a dedicated config file and read them from environment variables. Do not rely on the bundle's Configuration tree in a Laravel application.
- Does it support caching and rate limiting?
- The overview mentions caching support to reduce requests, but the assessment flags rate limiting, retries, and cache behavior as unclear. In Laravel, implement caching with Laravel's cache repository and add retry, backoff, and circuit breaking around HTTP calls. Cache reference data aggressively and cache flight status only briefly.
- Which FlightStats API endpoints does it cover?
- It is described as covering flight status lookups for arrivals, departures, and delays plus airport and airline metadata. The exact FlightStats API version and authentication model are not confirmed in the assessment. Audit the source before adopting it, or use it as a specification for a thin client.
- Is spiicy/flightstats-bundle maintained and safe for production?
- The assessment describes it as effectively unmaintained, with 1 star, 0 dependents, and no recent maintenance evidence. There is no disclosed security process and license clarity is not confirmed. Treat it as a code sample rather than a production dependency, and plan to own all future changes.
- What FlightStats authentication model does it use?
- The assessment explicitly flags this as a key question: legacy appId/appKey versus OAuth2 client credentials. The provided context does not confirm which model or API version is targeted. Verify this before adopting, because FlightStats has changed authentication and versioned or retired endpoints over time.
- Should I wrap it or rewrite a Laravel FlightStats client?
- For most Laravel teams, rewriting a thin client is often the lowest total cost because the bundle is small and heavily Symfony-coupled. Wrapping is viable for a short-lived prototype if the core services use constructor injection and avoid container lookups. Forking into a first-party package makes sense when you need long-term ownership and Laravel-native HTTP, cache, and queue primitives.
- How should I test a FlightStats integration in Laravel?
- Use recorded fixtures or sandbox responses behind an internal interface such as FlightStatusProvider, then bind a fake implementation in tests. Add contract tests for response mapping and failure modes such as auth expiry, 429 responses, and null flight statuses. Avoid live vendor calls in CI unless sandbox credentials and quotas are confirmed.
Weaver
How can I help you explore Laravel packages today?