Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Video Widget

Video Widget Laravel Package

friendsofvictoire/video-widget

A small Laravel package that provides a reusable video widget for embedding and playing videos in your app. Drop it into your views to render video content without writing custom markup, keeping playback setup and presentation in one place.

View on GitHub
Deep Wiki
Context7

Victoire DCMS Video widget

Frequently asked questions about Video Widget
Is friendsofvictoire/video-widget a Laravel package?
No, it is a Symfony bundle (WidgetVideoBundle) for the Victoire CMS, despite being labeled as a Laravel package in some intakes. It ships no Laravel service provider, auto-discovery entry, publishable config, or Blade views. In a Laravel app it will not install, boot, or render.
Can I install friendsofvictoire/video-widget in Laravel 10 or 11?
Unlikely. Victoire is Symfony 2/3-era, so Composer constraints likely cap PHP at 7.x and Symfony at ^2.7|^3.x, which conflicts with Laravel 10/11 requiring PHP 8.1+ and Symfony 6/7. Composer require will likely fail on platform constraints, and --ignore-platform-reqs just relocates the failure to runtime in a hard-to-debug place.
What does the Video Widget actually do?
It provides a reusable widget for embedding responsive video players such as YouTube and Vimeo in Victoire CMS pages. The bundle includes a small config object (provider plus URL or ID), an editor form, and a render template. That pattern is framework-agnostic, but the bundle itself is Symfony/Victoire-specific.
How do I embed a YouTube or Vimeo video in a Laravel Blade view without this package?
Build a small Blade component or directive that accepts a provider and video ID or URL, validates them, and renders a responsive iframe with aspect-ratio CSS. Handle consent gating, youtube-nocookie domains, frame-src CSP, and lazy loading as first-party concerns. This is roughly 150 to 200 lines and avoids taking on an abandoned dependency.
Is friendsofvictoire/video-widget maintained?
There is no visible maintenance, no security response process, and near-zero adoption (1 star, 0 dependents). If you adopt it, you own a fork including security patching and framework-version tracking. That is a lot of ownership for what is fundamentally a templated iframe.
What are the alternatives to friendsofvictoire/video-widget for Laravel?
Use a maintained embed library such as oscarotero/embed for oEmbed resolution, plus your own Blade component for rendering, consent, and CSP. If you need editor integration, map the same pattern to a Filament field or Livewire component. The key is to own the small rendering layer rather than depend on an abandoned bundle.
Does the Video Widget handle GDPR consent and YouTube no-cookie embeds?
Almost certainly not. Abandoned bundles rarely solve consent gating, youtube-nocookie domains, frame-src CSP, or lazy loading. These are application concerns you must implement regardless of package choice, so the time saved by the package shrinks toward zero.
What are the requirements for using this package natively?
You need a Symfony/Victoire application, likely on Symfony 2/3-era constraints with PHP 7.x. Victoire itself is EOL-era, so native use is only realistic if you already have a Victoire app and accept the legacy stack. It is not a viable path for new Laravel or Symfony 6/7 projects.
Should we adopt this package or build our own video widget?
Treat it as a design reference, not an adoption candidate, unless you have an actual Victoire app in the estate. The capability is commoditized and reproducible in 1 to 2 engineer-days. Build a small first-party component for Blade, Filament, or Livewire and assign ownership to the team that will maintain it.
How do I test a video widget component in Laravel?
Test that the component renders the expected provider URL, applies aspect-ratio classes, and respects consent and CSP settings. Use feature tests with assertSee for the iframe src and attributes, and unit-test URL and provider parsing. Mock any oEmbed HTTP calls if you add thumbnail or title resolution.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons