Weave Code
Streamlabs Laravel Package
socialiteproviders/streamlabs
A Laravel Socialite provider that adds Streamlabs OAuth login to your app. Install via Composer, wire up the Streamlabs listener with Socialite Providers, and authenticate users through the familiar Socialite API.
[READ ONLY] Subtree split of the SocialiteProviders/Streamlabs Provider (see SocialiteProviders/Providers)
Frequently asked questions about Streamlabs
- What is socialiteproviders/streamlabs used for?
- It is a Laravel Socialite provider that adds Streamlabs OAuth login to your application. It handles the redirect, callback, token exchange, and user normalization so you can call Socialite::driver('streamlabs') like any other provider. It is not a Streamlabs API client, so donations, alerts, and channel data calls remain your application's responsibility.
- How do I install socialiteproviders/streamlabs?
- Install it with Composer using composer require socialiteproviders/streamlabs. Then register the Streamlabs listener for the SocialiteWasCalled event in your application's event service provider or bootstrap configuration. You must also add Streamlabs client credentials and a redirect URI to your configuration.
- How do I configure Streamlabs OAuth credentials for Laravel Socialite?
- Create an application in the Streamlabs developer console to obtain a client ID and client secret, and allowlist your callback URL as the redirect URI. Add those values to your services configuration and expose them through environment variables. Wire the Streamlabs listener so Socialite knows which provider class to use when the driver is requested.
- Which Laravel and Socialite versions does this package support?
- The package's composer.json is the source of truth for supported Socialite, PHP, and Laravel constraints. Version 4.2.0 is a minor release, but it changes the external Streamlabs API version it consumes, so confirm compatibility against your locked dependencies rather than assuming. This provider is intended for applications already using Laravel Socialite.
- Is this an official Streamlabs or Laravel package, and what are the alternatives?
- No. It is a community SocialiteProviders package and a subtree split of the SocialiteProviders/Streamlabs provider, not a first-party Laravel or Streamlabs release. Alternatives include another Socialite provider, a custom Socialite driver, or a direct OAuth implementation. If your app already uses Socialite, this adapter is the least-effort path.
- What changed in 4.2.0 when the provider moved to the Streamlabs v2 API?
- The release note is effectively a single line saying it uses the v2 API, with no changelog or migration mapping. That means a minor version bump may carry behaviorally breaking changes if v2 alters response shape, field names, identifiers, scopes, or token lifetimes. Read the diff and test real login flows rather than trusting the semver number.
- Will existing users be duplicated after upgrading to Streamlabs v2?
- That is the highest-severity risk. If Streamlabs returns a different provider user ID or ID namespace under v2, applications that persisted provider_id from v1 may fail to match returning users and could create duplicate accounts. Plan a deduplication or mapping strategy and verify with real Streamlabs logins before and after upgrading.
- Will users have to re-authorize or re-consent after the Streamlabs API change?
- It depends on whether the requested scopes and consent behavior changed under v2. The release notes do not document scope changes, so you must inspect the provider code and verify against the Streamlabs developer console. If scopes changed, existing connected users may be forced through re-consent on their next login.
- How can I test Streamlabs login in a Laravel application?
- Mock or fake the Socialite driver in feature tests so your callback logic runs against a controlled user payload. Add unit tests around how you persist the provider ID and normalize profile fields, because those are the paths most likely to break across API versions. A manual OAuth round-trip against a Streamlabs test app is still required because token exchange and consent happen externally.
- Is socialiteproviders/streamlabs actively maintained, and what if it is abandoned?
- Maintenance confidence is limited here: the 4.2.0 release has a one-line note and no migration documentation, which is a release-process maturity signal. Check the GitHub repository for recent commits, issue responsiveness, and release cadence before committing. If it is abandoned, you can fork the provider, vendor the subtree, or implement the Streamlabs Socialite driver directly.
Weaver
How can I help you explore Laravel packages today?