- Can I install inori/twitter-app-bundle in a Laravel app?
- No. It is a Symfony2 bundle that registers through the AppKernel and ships a DependencyInjection extension with YAML service configuration in Resources/config/services.yml. Laravel has no bundle registry, compiler passes, or YAML container, so there is no install-register-ship path. Composer dependency resolution also fails against modern Laravel, making it a rewrite rather than an integration.
- Does inori/twitter-app-bundle support Laravel 9, 10, or 11?
- No. Its Symfony2-era constraints (symfony/framework-bundle ~2.x, http-kernel ~2.x) collide with the Symfony ^6 components Laravel 9+ requires. Forcing it would regress the whole application to a PHP 5.5-7.0 stack just to enable one feature. Treat the package as incompatible with any current Laravel version.
- Is inori/twitter-app-bundle abandoned or still maintained?
- It is effectively abandoned: archived, around 7 stars, zero dependents, no tests, no CI badge, and no CVE response path. This is a security-sensitive surface handling OAuth tokens and outbound credentialed calls, and it is owned by nobody. That makes it unsuitable as a production dependency regardless of feature fit.
- What is the Laravel equivalent of this Symfony Twitter bundle?
- The recoverable value is roughly 30 lines of idiomatic Laravel: a config/twitter.php backed by env() and config:cache, plus a service provider binding a singleton TwitterClient to a TwitterClientContract interface. Put a maintained client underneath, such as abraham/twitteroauth for app-level calls or Laravel Socialite for user-delegated flows. Do not wrap a wrapper.
- Does inori/twitter-app-bundle still work with the X/Twitter API?
- It wraps a twitteroauth client targeting the v1.1 REST endpoints. Since the post-2023 X access-tier restructuring, many write endpoints sit behind paid plans and much of v1.1 is deprecated. Confirm you have a funded tier that still exposes the endpoints you need before spending any engineering time.
- How do I implement Twitter/X OAuth login in Laravel instead?
- Use Laravel Socialite for user-delegated OAuth flows such as social login. This bundle's OAuth support is tied to Symfony2 DI conventions and cannot be reused directly in Laravel. For app-only publishing, use abraham/twitteroauth at its current major version or Laravel's HTTP client for direct calls.
- How should I store Twitter API credentials in a Laravel app?
- Do not follow this bundle's pattern of container parameters, which is an audit finding for SOC2 or ISO-scoped products. Keep non-secret configuration in env() plus config:cache, and put API keys and OAuth tokens in a secrets manager such as Vault, AWS Secrets Manager, or encrypted config. Never commit credentials to version control.
- Will inori/twitter-app-bundle run on PHP 8.2?
- No. The code is from the PHP 5.5-7.0 era and PHP 8.2+ will emit deprecations and fatals on untyped properties and array-offset response parsing. Because the repository is archived, there is no path to fixes. Upgrading it means forking and maintaining the code yourself.
- How much work is it to replace this bundle in a Laravel application?
- Plan for one to two days of idiomatic Laravel work, not a port. The scope is a config file, a singleton service provider binding behind a contract, a maintained Twitter client, and queued jobs with retry/backoff and a rate-limit token bucket. That is far cheaper than porting Symfony2 wiring and owning it indefinitely.
- Are there maintained alternatives to inori/twitter-app-bundle?
- Yes. Use abraham/twitteroauth at its current major version for app-level API calls and Laravel Socialite for user-delegated OAuth, with Laravel's HTTP client for any custom requests. This bundle's only legitimate uses are as a short reference for DI wiring patterns or as an evaluated-and-rejected entry in an ADR. It is a historical artifact, not a candidate dependency.