- What is mortezamasumi/fb-suite and what packages does it bundle?
- fb-suite is a Composer meta-package that pulls in the family of fb-* Laravel packages through a single dependency instead of requiring each module individually. Its visible dependency is fb-auth, which provides the OTP-based authentication stack, and the remaining fb-* modules are tracked at the suite level. Because it is an umbrella package, the exact module list is determined by the maintainer's release, so check composer.json and composer.lock after install to see what actually resolved.
- How do I install fb-suite in a Laravel application?
- Install it with composer require mortezamasumi/fb-suite, then run php artisan vendor:publish for the tagged config and migration files and follow up with php artisan migrate. The package follows standard Laravel service-provider auto-discovery, so manual provider registration is normally unnecessary. Confirm your PHP and Laravel versions fall inside the supported range before running the update.
- Which Laravel and PHP versions does fb-suite support?
- fb-suite inherits most of its framework constraints from the fb-* packages it depends on, especially fb-auth, so the effective support matrix is whatever those packages declare. Version 5.0.3 raises the fb-auth floor to ^5.1.5, and a narrowed PHP or Laravel constraint in that release is the most likely source of an unexpected Composer conflict. Read the composer.json constraints of the resolved fb-auth version rather than assuming the suite's own.
- What changed in fb-suite 5.0.3 and do I need to upgrade?
- 5.0.3 is a single-commit patch that bumps the fb-auth requirement to ^5.1.5 so consumers receive an upstream fix for null OTP handling in the password reset flow. There are no new features, declared breaking changes, or config changes attributable to fb-suite itself. Upgrading is advisable because until the exact failure mode is clarified, the null-OTP defect should be treated as a potential authentication bypass rather than a cosmetic bug.
- How do I make sure Composer actually installs fb-auth 5.1.5 or higher?
- Bumping only the fb-suite constraint in composer.json is not enough, because Composer may keep the already-locked fb-auth version. Run composer update mortezamasumi/fb-suite mortezamasumi/fb-auth --with-dependencies, then inspect composer.lock to confirm fb-auth resolved at 5.1.5 or above. Also verify that no other fb-* package was silently downgraded or removed during the resolution.
- Can I use fb-suite without Filament, or install only one fb-* package?
- fb-suite is an aggregation layer, so installing it adopts every module the maintainer bundles, including any Filament admin integration that ships with those packages. If you only need Facebook authentication, depending on fb-auth directly gives you a smaller, more controllable surface and a narrower blast radius for upstream regressions. Use fb-suite when the convenience of a pre-integrated, consistently configured stack outweighs that optionality.
- Is fb-suite safe to run in production?
- The package itself is a thin meta-package, so the production risk profile is really the risk profile of the fb-* modules it pins, and the suite couples your login and reset surface to the maintainer's release cadence. Before adopting it, evaluate bus factor, CI coverage across Laravel majors, release cadence, and whether there is a security disclosure channel. For a core authentication dependency, those governance questions matter more than the code diff in any single patch.
- How do I configure Facebook app credentials with fb-suite?
- Configuration is published to your config directory through the standard vendor:publish flow, where you add your Facebook app ID, app secret, and OAuth redirect URI, typically sourced from environment variables. Because fb-auth and the other fb-* modules are designed to share consistent configuration, you should set credentials once at the suite level rather than per package. Keep the secret and any access tokens out of version control and rotate them if they were ever committed.
- How do I test Facebook authentication flows with fb-suite?
- Mock Graph API calls with Laravel's Http::fake in feature tests rather than hitting Facebook, and assert that OTP and token validation paths return the expected results. Cover null, missing, expired, and reused OTP cases explicitly, since that is exactly the class of bug patched in fb-auth 5.1.5. Run the suite in CI across the Laravel and PHP versions you actually deploy so constraint drift shows up before release.
- What are the alternatives to fb-suite?
- The main alternative is depending on the individual fb-* packages directly, most commonly fb-auth, which removes the umbrella layer and lets you control versions per capability. Laravel Socialite remains the general-purpose option for Facebook login if you do not need the suite's OTP-based password reset workflow. A custom in-house implementation is worth considering when authentication is core to your product and you need full control over reset and OTP logic.