Weave Code
Vimeo Bundle Laravel Package
requestlab/vimeo-bundle
Symfony bundle that integrates Vimeo’s API into PHP applications, offering services for video uploads, metadata retrieval, and embed configuration. Streamlines setup and dependency injection for Vimeo-powered features.
A Symfony 2 Bundle to use Vimeo API
Frequently asked questions about Vimeo Bundle
- Is requestlab/vimeo-bundle a Laravel package?
- No, it is a Symfony 2 bundle, not a Laravel package. Laravel does not natively load Symfony bundles, so you cannot install and register it like a Laravel service provider. To use it in Laravel you would need to port the API client code or wrap it yourself.
- How do I install requestlab/vimeo-bundle with Composer?
- Install it via Composer in a Symfony 2 or 3 application and register the bundle in the kernel. In Laravel, installation will likely fail because of Symfony 2 component constraints and older PHP version requirements. Run composer why-not requestlab/vimeo-bundle against your target app before attempting adoption.
- Does requestlab/vimeo-bundle support Laravel 10 or Laravel 11?
- No, it does not support modern Laravel versions. It targets Symfony 2-era components and older PHP ranges, which conflict with Laravel 10 and 11 requirements such as PHP 8.1+ and current Illuminate components. Use the official vimeo/vimeo-api SDK behind your own Laravel service instead.
- Which Vimeo API version does requestlab/vimeo-bundle target?
- The bundle is old and sits at or before Vimeo's API v3 transition, so its auth flows and upload semantics may be outdated. You should verify the endpoint usage and auth model before relying on it. Modern integrations should use the official SDK or current Vimeo API documentation.
- What features does requestlab/vimeo-bundle provide for Vimeo videos?
- It provides config-driven API client setup, video upload and management, metadata retrieval, processing status checks, and embed configuration. It is designed as a Symfony service with dependency injection. Review the actual implemented operations carefully because the package is dormant.
- Can I use requestlab/vimeo-bundle inside a Laravel service provider?
- Technically you could copy the client layer into a Laravel service provider, but the bundle's main value is its Symfony wiring, which does not port. The remaining API-calling code is thin, so wrapping the official Vimeo SDK is usually the better trade. If you fork it, drop the Symfony dependency injection and config tree.
- Is requestlab/vimeo-bundle maintained and safe for production?
- It appears dormant, with zero stars, zero dependents, and a single maintainer. Symfony 2 reached end of life in 2018, so inheriting its components widens CVE exposure. There is no production validation signal, so avoid direct adoption for new production work.
- What are alternatives to requestlab/vimeo-bundle for Laravel?
- The official vimeo/vimeo-api SDK is the recommended alternative because it is maintained and supports current PHP and API versions. Wrap it behind an internal VimeoClient interface and bind that in Laravel's container. You can use the bundle only as a design reference for endpoints and response modeling.
- How do I test Vimeo uploads with requestlab/vimeo-bundle?
- The package likely requires live Vimeo credentials for upload and status flows unless it mocks HTTP internally. Check whether tests exist and whether they isolate the HTTP client. In Laravel, define a fake implementation of your own VimeoClient interface for tests.
- Should I adopt or fork requestlab/vimeo-bundle?
- Do not adopt it directly for Laravel. Either use the official Vimeo SDK behind an internal contract or fork the API layer, remove Symfony wiring, and package it as a Laravel service provider. Only consume the bundle directly inside a legacy Symfony 2 or 3 app as a short-lived bridge.
Weaver
How can I help you explore Laravel packages today?