- Can I install gulaandrij/google-sheets-bundle in a Laravel application?
- No. It is a Symfony bundle that depends on symfony/framework-bundle and registers its services through a Symfony DI extension, so it is not a Laravel package and cannot be installed into a Laravel app as-is. For Laravel, use revolution/laravel-google-sheets or google/apiclient directly and keep your own small adapter. The bundle is useful mainly as a reference for how to wrap the underlying client.
- What does gulaandrij/google-sheets-bundle add over revolution/laravel-google-sheets?
- Its main content is Symfony DI wiring: a Configuration tree, service definitions, and a compiler pass that aliases a SheetsService. The higher-level service may normalize ranges or wrap append semantics, but the evaluation found no evidence of batching, caching, or retry logic. If you are in Laravel, there is little to port beyond the API shape; you can reimplement that surface in a few hundred lines. Verify the actual service code before assuming it adds features.
- How do I install and configure gulaandrij/google-sheets-bundle in Symfony?
- Install it with Composer, enable the bundle in config/bundles.php, and provide your Google service-account credentials through the bundle configuration. The bundle registers the Google API client and the SheetsService so you can inject the service rather than building the client yourself. Outside Symfony you would need to replicate that wiring manually.
- Which Symfony and Laravel versions does gulaandrij/google-sheets-bundle support?
- The package constrains Symfony components such as symfony/config, symfony/dependency-injection, and symfony/framework-bundle, and the evaluation warns those constraints can block Symfony upgrades in a Laravel app. It is not a Laravel package, so Laravel version support is indirect: it comes only through the underlying revolution/laravel-google-sheets dependency. Check Packagist for the exact supported ranges before installing.
- How does authentication to Google Sheets work with this bundle?
- It uses Google service-account authentication: create a GCP project, enable the Google Sheets API, create a service account, download the JSON key, and point the bundle configuration at that key. Then share the target spreadsheet with the service-account email address, which is the step most first attempts miss. The bundle handles wiring the Google client, but you still own key rotation and GCP provisioning.
- Does gulaandrij/google-sheets-bundle support batch reads and writes or retry/backoff?
- The evaluation found no visibility into batch request support, exponential backoff, or Retry-After handling for 429/503 quota errors. Those behaviors materially affect correctness for large exports and multi-write workloads. Inspect the service code and the underlying revolution/laravel-google-sheets implementation before relying on it. If you need batching or retries, implement them in your own adapter.
- Is gulaandrij/google-sheets-bundle safe for production use?
- Treat it with caution. It has zero stars, zero dependents, a single author, and no external security review, and the evaluation flags a release-date anomaly (2026-06-09) to verify on Packagist. More importantly, Google Sheets is a reporting sink or low-volume store, not a system of record; avoid high write volume, multi-writer concurrency, or transactional requirements. The blast radius is low only if you copy a small surface rather than depend on it at runtime.
- What is the best alternative for reading and writing Google Sheets in Laravel?
- For Laravel, use revolution/laravel-google-sheets, which provides the service provider, facade, and config/google-sheets.php integration, or use google/apiclient directly. Wrap whichever you choose behind a locally owned SheetGateway interface and one adapter class. That keeps the Google-specific code small and testable, and avoids pulling Symfony framework components into Laravel.
- How do I test Google Sheets integration in Laravel without hitting the real API?
- Put Google Sheets calls behind your own SheetGateway interface and fake that interface in feature tests. For lower-level tests, inject a mocked Google client or mock the Guzzle handler used by google/apiclient. The Symfony bundle itself provides no Laravel test helpers, so do not expect testing utilities from it. This approach also lets you assert range normalization and append behavior deterministically.
- Is gulaandrij/google-sheets-bundle maintained, and should I depend on it?
- Maintenance risk is high: one author, no dependents, no issue history, and a suspicious release date that should be checked against the Packagist record and commit history. The evaluation recommends against a runtime dependency and suggests using it as a reference implementation only. If you copy code, confirm author identity and license first, and keep the copied surface small so it is reversible.