- Is fungio/google-calendar-bundle compatible with Laravel 10 or 11?
- No. It is a Symfony 3 bundle with Bundle classes, DependencyInjection extensions, and YAML service definitions, so Laravel cannot consume it as a package. Its Composer constraints will likely conflict with the Symfony 6 or 7 components modern Laravel uses. Treat adoption as a port, not an install.
- Can I install fungio/google-calendar-bundle with composer require in a Laravel app?
- A clean composer require will likely fail because the bundle targets Symfony 3 and pins end-of-life framework constraints. Even if dependency resolution succeeds in an isolated sandbox, you still get no Laravel service provider, facade, or publishable config. Run the install in a throwaway project before assuming it works.
- What does fungio/google-calendar-bundle actually contain?
- The useful part is a thin service layer wrapping Google's PHP client for authentication, calendar management, and event creation or sync. The rest is Symfony bundle plumbing: a Bundle class, a DependencyInjection extension, and YAML service wiring. There is no evidence of substantial IP such as recurrence handling, timezone normalization, or multi-calendar fan-out.
- What Laravel package should I use for Google Calendar instead?
- Use google/apiclient v2 with your own Laravel service provider as the baseline. If you want calendar CRUD without writing the wrapper, evaluate a maintained Laravel-native package such as spatie/laravel-google-calendar and check its release cadence and issue latency first. Either option beats porting an abandoned Symfony 3 bundle.
- How much work is porting this Symfony bundle to Laravel?
- Expect roughly 3 to 5 engineer-days plus about a day of test repair, versus under a day for a first-party google/apiclient wrapper. You must copy the service classes into app/Services, strip Symfony DependencyInjection and Config references, replace YAML parameters with a Laravel config file and service provider, and rewrite tests off Symfony KernelTestCase. Only do this if a spike finds non-trivial domain logic worth keeping.
- Does fungio/google-calendar-bundle support modern Google OAuth2 and syncToken?
- It almost certainly pins google/apiclient v1.x or early v2.x, predating current OAuth2 token handling, incremental syncToken semantics, and push notification channel behavior. That means auth and sync code may need rewriting even after the Symfony plumbing is removed. Verify the exact google/apiclient constraint in composer.json before relying on it.
- Is fungio/google-calendar-bundle maintained and safe for production?
- Signals say no: about 10 stars, zero dependents, and no meaningful issue history, which is the profile of an abandoned side project. Symfony 3 has been end-of-life since November 2021, so upstream security patching is gone. Production use would require forking and owning the code permanently.
- What PHP version does fungio/google-calendar-bundle require?
- The constraints are likely PHP 5.6 or 7.0-era, while modern Laravel requires PHP 8.1 or newer. That mismatch alone can block installation or force upgrades across the copied code. Check composer.json for the exact php constraint and syntax level before planning a port.
- Should I fork fungio/google-calendar-bundle or write my own Google Calendar integration?
- Write your own unless a short spike proves the bundle contains real IP you cannot reproduce quickly. The wrapper is typically 300 to 600 lines against google/apiclient, reproducible in a day or two with current auth and sync behavior. Forking means permanent ownership of end-of-life Symfony constraints and stale Google client code.
- Can I use this bundle for the OAuth2 flow only, without calendar sync?
- You can, but it is not a good trade. An OAuth2 flow is about a 50-line controller with google/apiclient and Laravel's HTTP and session handling. Pulling in a Symfony 3 bundle for that adds end-of-life transitive dependencies and porting work for no real benefit.