- Is vinkla/facebook still maintained?
- No. The package is archived and its last release was in 2019, so it receives no security fixes, Laravel or PHP compatibility updates, or handling for Facebook Graph API deprecations. Treat it as a legacy dependency and plan a replacement rather than adopting it for new work.
- How do I install vinkla/facebook in Laravel?
- Install it with Composer using composer require vinkla/facebook, then publish the package config file, typically with php artisan vendor:publish, to set your Facebook app ID, secret, and redirect URI. The package registers its service provider and Facebook facade automatically. Because it is archived, verify its Composer constraints against your PHP and Laravel versions before installing.
- Which Laravel and PHP versions does vinkla/facebook support?
- The package documentation does not cover modern framework versions, and the last release dates to 2019, so it likely targets older Laravel 5-era conventions and pre-PHP 8 runtimes. It is unlikely to be tested against PHP 8.x or Laravel 9, 10, or 11. Check the Composer constraints and transitive dependencies carefully before committing to it.
- How do I configure Facebook app credentials with vinkla/facebook?
- Publish the package config file and set your Facebook app ID, app secret, and redirect URI, preferably per environment using .env values. The service provider uses that configuration to bind a configured Facebook SDK client into Laravel's container. Keep credentials out of source control and separate them for local, staging, and production environments.
- How do I call the Facebook Graph API using the Facebook facade?
- Resolve the configured SDK client through the Facebook facade or Laravel's container, then use the official Facebook SDK methods to make Graph API requests. For maintainability, wrap those calls behind an internal interface instead of scattering facade usage through controllers, jobs, and domain services. This also makes it easier to replace the archived bridge later.
- Can I use vinkla/facebook for Facebook login and OAuth in Laravel?
- In principle yes, because the bridge exposes the official Facebook SDK's OAuth helpers for generating login URLs and handling callbacks. However, for social login as a core capability, Laravel Socialite is the safer and better-supported choice. This package is archived and should not be used for new OAuth implementations.
- How do I test code that uses vinkla/facebook?
- The package does not ship dedicated test helpers, but the container-resolved client can be mocked or swapped using Laravel's container and facade faking patterns. A stronger approach is to introduce an internal FacebookClient interface and write contract tests with mocked HTTP responses rather than depending on live Graph API calls. That boundary also simplifies future replacement.
- What are the best alternatives to vinkla/facebook for Laravel?
- Use Laravel Socialite for Facebook login, and the current official Facebook SDK for PHP or a thin, version-pinned HTTP client for Graph API access. If you need a Laravel bridge, evaluate community packages that explicitly support your current Laravel and PHP versions. Always check maintenance status, recent releases, and Graph API version support before choosing.
- Is vinkla/facebook safe to use in production?
- It carries high lifecycle risk because it is archived, receives no security or compatibility fixes, and does not track Facebook Graph API changes. If it is already in production, freeze it at a known compatible version, contain it behind an adapter, and plan a migration. Do not introduce it into new development.
- How do I migrate away from vinkla/facebook?
- Inventory all facade, config, and container-binding usages, then freeze the dependency at a compatible version. Introduce an internal FacebookClient interface around login, token handling, and Graph calls, move callers to that interface, and add contract tests with mocked responses. Replace the bridge implementation with Laravel Socialite or a current Graph client, verify in staging with Facebook test users, and remove the package only after parallel validation.