Weave Code
Twitter Laravel Package
socialiteproviders/twitter
Twitter/X OAuth provider for Laravel Socialite. Add Twitter login to your Laravel app with a drop-in driver supporting OAuth 1.0a and OAuth 2.0, letting users sign in with their Twitter accounts quickly and securely via the familiar Socialite API. Simple to install and configure.
[READ ONLY] Subtree split of the SocialiteProviders/Twitter Provider (see SocialiteProviders/Providers)
Frequently asked questions about Twitter
- How do I install socialiteproviders/twitter in a Laravel app?
- Install it with Composer using composer require socialiteproviders/twitter, alongside laravel/socialite. Because this repository is a read-only subtree split of the SocialiteProviders/Twitter provider, the package itself is small and only adds the driver. After installing, register the provider in the SocialiteProviders event listener pattern and configure your X app credentials in .env. Commit both composer.json and composer.lock so the resolved version is reproducible across environments.
- How do I register the Twitter provider with Laravel Socialite?
- SocialiteProviders packages are registered by listening for the SocialiteWasCalled event and extending Socialite with the Twitter driver, typically in a service provider or the SocialiteProviders listener list. Once registered, you call Socialite::driver('twitter') in your controller exactly as you would with any other provider. Make sure the listener is registered before the OAuth callback route is hit, or Socialite will not recognize the driver.
- Which environment variables does the Twitter provider need?
- You need to add your X/Twitter app credentials to .env, conventionally TWITTER_KEY (consumer key or client ID), TWITTER_SECRET (consumer secret or client secret), and TWITTER_REDIRECT_URI. These values must match the callback URL registered in the X developer portal exactly, including scheme and trailing slashes. Also add the corresponding keys to config/services.php if your app caches configuration, and run php artisan config:clear after changes.
- Does this package support OAuth 1.0a or OAuth 2.0?
- The provider supports both OAuth 1.0a and OAuth 2.0 flows, but which one you get depends on how the driver is configured and on your X app settings. OAuth 1.0a uses the consumer key and secret pair, while OAuth 2.0 uses client ID, client secret, and scopes such as users.read and tweet.read. Confirm the OAuth mode your product requires before you build the flow, because the token handling and the identity payload returned to your callback differ between the two.
- Is socialiteproviders/twitter compatible with Laravel 11 and the latest Socialite?
- The last tagged release was in May 2023, so you should not assume compatibility with newer Laravel or Socialite majors without testing. Pin the package version in Composer and verify its constraints against your target Laravel, PHP, and Socialite matrix. Check the parent SocialiteProviders/Providers monorepo for unreleased fixes, since this split repository may lag behind it. A quick staging integration test of the full callback flow is the fastest way to confirm compatibility.
- Do I still need this package if Laravel Socialite already has a Twitter driver?
- Laravel Socialite has shipped official X/Twitter support, so for simple login-only use cases the built-in driver may be sufficient and this package could be redundant. Evaluate both options against the OAuth mode, scopes, and user payload you need from the X API. If you adopt this package, introduce it behind an internal SocialAuthProvider abstraction so you can switch back to the built-in driver without rewriting controllers. That abstraction also makes it easy to support other providers consistently.
- How should I test the Twitter login flow before going live?
- Create a separate X developer app for staging with its own callback URL and credentials, then prove the complete authorization and callback round trip there. Write integration tests covering success, user denial, callback URL mismatch, revoked access, and a provider outage or error response from X. Also test account linking: what happens when the same Twitter account logs in twice, or when the email already belongs to a local user. Roll out behind a feature flag with telemetry so you can disable the flow quickly if something breaks.
- What production risks should I watch out for with this provider?
- The main risks are external: X/Twitter API and policy changes, OAuth mode mismatches, revoked or rotated app credentials, callback URL drift, and rate limiting or app tier restrictions. The PHP code surface is small and OAuth handshakes are low-volume, so the practical scaling limits come from X's quotas rather than from the package. Build a runbook covering credential rotation, callback URL changes, app suspension, and login failures. Monitor failure rates on the callback route so silent breakage is caught early.
- Who maintains socialiteproviders/twitter and how do I get fixes merged?
- This repository is a read-only subtree split, which means issues and pull requests belong in the parent SocialiteProviders/Providers monorepo, not here. Star counts and activity on the split repo are not representative of real maintenance, so track upstream activity instead. Because the last release is from May 2023, plan for internal ownership: assume you may need to fork the provider or replace it with a custom Socialite driver if maintenance stalls. Keep the provider behind your own interface so that fork or replacement is a contained change.
- What alternatives exist if this package stops working for me?
- The most common alternatives are Laravel Socialite's built-in X/Twitter driver, a small custom Socialite provider written in-house, or a dedicated X API client if you need posting and API access beyond authentication. If you only need login, switching between these is usually a matter of changing the driver name and the returned user mapping. Keep an internal SocialAuthProvider interface and store provider-agnostic user identities, which lets you migrate or support multiple providers without touching account data. Feature-flag the change and run both configurations in staging before cutting over.
Weaver
How can I help you explore Laravel packages today?