- Can I use hautelook/instagram-bundle in a Laravel application?
- It is a Symfony bundle, not a Laravel package, so Laravel will not register its bundle class, DI extension, or configuration tree. Composer may install the files, but there is no service provider or facade to wire it into Laravel. Treat it as reference code rather than a dependency.
- Does hautelook/instagram-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets old Symfony and PHP constraints, likely Symfony 2.7 or 3.x and PHP 5.6 through 7.x, which will not resolve cleanly on PHP 8.2 or 8.3 with Laravel 10 or 11. Its transitive Guzzle version can also conflict with Laravel's Guzzle 7 constraint. A Composer install will often fail resolution or force unsafe downgrades.
- Is the Instagram API used by this bundle still available?
- No. The bundle targets the legacy Instagram Platform API at api.instagram.com/v1, which was retired. Instagram Basic Display was also deprecated in late 2024 in favor of the Instagram Graph API, which requires Facebook Login and Business or Creator accounts. Any OAuth flow or endpoint calls in the bundle should be considered obsolete.
- How do I install hautelook/instagram-bundle?
- You would normally install it with Composer and register the bundle in a Symfony Kernel, but that workflow does not apply to Laravel. Even in Symfony, the package is unmaintained and its API target is dead, so installation is not recommended. If you only need reference material, clone the repository instead of adding it as a dependency.
- What should I use instead of hautelook/instagram-bundle for Instagram feeds in Laravel?
- Build a native Laravel integration around the Instagram Graph API. Use Laravel Socialite for Facebook or Instagram OAuth, the Http facade for Graph API calls, and config/services.php plus .env for credentials. Port only framework-agnostic normalization or pagination logic from the bundle, if any is useful.
- Does hautelook/instagram-bundle handle token refresh and long-lived Instagram tokens?
- The bundle predates the current Graph API token model and likely assumes manually replaced long-lived tokens rather than implementing robust refresh. Modern Instagram long-lived tokens last about 60 days and should be refreshed on a schedule. Store tokens encrypted with expiry and run a scheduled refresh job well before expiration.
- Is hautelook/instagram-bundle maintained or safe for production?
- It shows no stars, zero dependents, and no active maintainer, which are strong abandonment signals. The higher production risk is that its endpoints are retired, so API calls will fail regardless of code quality. Unmaintained transitive dependencies, likely including an old Guzzle, add known CVE exposure and conflict with modern Laravel.
- Can I test hautelook/instagram-bundle in a Laravel test suite?
- Not meaningfully, because Laravel cannot boot the Symfony bundle's DI extension or configuration tree without a bridge. Unit-testing ported domain classes is possible if you strip container annotations and framework coupling. For new code, use Laravel's Http fake and Socialite fakes to test your own Graph API adapter.
- What PHP and Symfony versions does hautelook/instagram-bundle require?
- The repository is from the HauteLook era and likely constrains PHP to 5.6 through 7.x and Symfony to 2.7 or 3.x, though you should verify composer.json. Those constraints will not resolve on PHP 8.2 or 8.3 with Laravel 10 or 11. Check the Guzzle constraint too, because Guzzle 5 or 6 will fight Laravel's Guzzle 7 requirement.
- Is there a Laravel bridge that lets me run Symfony bundles like hautelook/instagram-bundle?
- A bridge such as laravel-symfony-bundle exists, but layering it over an abandoned bundle to reach a retired API compounds framework mismatch, dead endpoints, and dependency risk. It is not a practical migration path. A small native Laravel adapter is simpler, safer, and easier to maintain.