- What does the socialiteproviders/steem package do?
- It is a Socialite provider that adds Steem as an OAuth social-login driver in Laravel applications. It plugs into Laravel Socialite through the SocialiteProviders manager, letting you call Socialite::driver('steem') to redirect users and retrieve their profile. The package itself is a subtree split of the SocialiteProviders/Providers monorepo, so its code and release history mirror that upstream project.
- How do I install socialiteproviders/steem in a Laravel app?
- Install it with Composer using composer require socialiteproviders/steem, along with laravel/socialite and socialiteproviders/manager if they are not already present. Register the SocialiteProviders\Manager\SocialiteWasCalled event listener in your EventServiceProvider (Laravel 11+ event discovery may handle this automatically). Then add Steem client credentials to config/services.php under a steem key and clear your config cache.
- Which Laravel versions are supported by socialiteproviders/steem?
- The package is built for Laravel via Socialite, but the exact supported Laravel major matrix is not documented in the available material. Release 4.1.0 confirms PHP 8 support, yet a PHP 8-capable package can still carry Laravel version constraints that block Laravel 10 or 11. Check the package's composer.json constraints and run composer why-not before assuming compatibility with your Laravel version.
- Does socialiteproviders/steem support PHP 8?
- Yes, the 4.1.0 release note specifically states that it adds PHP 8 support, which removes the previous blocker for modern Laravel stacks. The note does not clarify whether this was only a widened platform constraint or whether internal code was reworked to be PHP 8-clean. Run your test suite with deprecation reporting enabled, especially on PHP 8.2+, to catch dynamic property or type-coercion issues.
- How do I configure the Steem driver credentials in Laravel?
- Add a steem entry to config/services.php containing your client_id, client_secret, and redirect URI, typically read from environment variables such as STEEM_CLIENT_ID, STEEM_CLIENT_SECRET, and STEEM_REDIRECT_URI. The redirect URI must exactly match the callback URL registered with your Steem OAuth application. After changing configuration, run php artisan config:clear so the new values are picked up.
- How do I use the Steem provider to log a user in?
- Use Socialite::driver('steem')->redirect() to send the user to Steem's authorization page, and handle the callback route with Socialite::driver('steem')->user(). That user object exposes the identifiers and profile fields returned by the provider, which you can map to your local user model. Because this is a SocialiteProviders driver, the SocialiteWasCalled event listener must be registered for the driver to resolve.
- How can I test Steem social login without hitting the real OAuth flow?
- Mock the Socialite driver in feature tests so your callback controller receives a fake user object instead of performing a live OAuth exchange. You can also assert that the redirect route returns the expected authorization URL. Keep a small manual smoke test against Steem's sandbox or a test application to verify real credential and redirect URI behavior, since package-level PHP 8 support claims do not guarantee every OAuth edge case is covered.
- What production risks should I check before adopting socialiteproviders/steem?
- Confirm the supported PHP and Laravel matrix, and pin the release line in composer.json rather than allowing broad updates. Inspect the lockfile delta and run composer why-not when moving to 4.1.0, since a PHP 8 support release can trigger transitive dependency upgrades. Also assess maintainer concentration and release cadence, because the available evidence is limited to a single release note and does not show CI coverage across PHP and Laravel versions.
- Are there alternatives to socialiteproviders/steem for Steem login in Laravel?
- The main alternative is writing a custom Laravel Socialite driver or a standalone OAuth client tailored to Steem's authorization endpoints. Other SocialiteProviders packages cover different platforms but will not provide Steem-specific profile mapping. If you need guaranteed long-term maintenance, compare the upstream SocialiteProviders/Providers repository activity and issue backlog before committing.
- How is socialiteproviders/steem maintained and released?
- This package is a read-only subtree split of the SocialiteProviders/Providers monorepo, so releases are generated from that upstream source rather than maintained independently. The available evidence covers only the 4.1.0 release note mentioning PHP 8 support, with no changelog history, CI matrix, or maintainer details provided. Track the upstream repository's commits and open issues to judge bus factor and how quickly PHP or Laravel compatibility problems are addressed.