Weave Code
Html Widget Laravel Package
victoire/html-widget
victoire/html-widget is a Laravel/PHP package for defining, managing, and rendering reusable HTML widgets. It helps embed custom markup cleanly while keeping widget content organized, reusable, and easy to integrate into dashboards, CMS blocks, and dynamic page sections.
At a glance
Frequently asked questions about Html Widget
- Is victoire/html-widget compatible with Laravel?
- No meaningful Laravel compatibility is claimed or evident. The package follows Symfony and Victoire bundle conventions, including Doctrine and Twig assumptions, rather than Laravel's container and Blade. Bridging those systems would cost more than implementing the feature natively.
- Can I install victoire/html-widget in a Laravel app with Composer?
- You can attempt a Composer require, but it is not a Laravel package. There is no Laravel service provider, package discovery, or Blade integration, and Composer may reject its old Symfony constraints on current PHP. Do not add it as a dependency for a Laravel feature.
- Does victoire/html-widget support Laravel 10 or 11?
- It should not be expected to support Laravel 10 or 11. The last release was August 2016 and the code is built for Symfony 2.x/3.x-era Victoire, not modern Laravel. Use a native Blade component for current Laravel versions.
- What does victoire/html-widget actually do?
- It is a Victoire CMS widget bundle for defining admin-managed HTML fragments and rendering them, historically through Twig and Symfony services. Its purpose is reusable raw HTML content, not a general Laravel widget API. In Laravel the same behavior is a small model, policy, Blade component, and sanitizer.
- Does victoire/html-widget support Blade templates?
- Available information points to Symfony/Twig conventions, not Blade-native rendering. There is no Laravel view integration or Blade component in the package. For data-aware HTML widgets in Laravel, use Blade components directly.
- Is victoire/html-widget maintained?
- No. The last release was August 2016, and the assessment notes 2 stars and 0 dependents. That means no upstream patching, community triage, or compatibility guarantees. Treat it as abandoned for dependency decisions.
- Is it safe to render raw HTML widgets with this package?
- The core use case is unescaped raw HTML, which creates an admin-privileged XSS surface. The evaluation found no visible sanitization story. If you implement the pattern, restrict authoring by permission and run a maintained sanitizer instead of rendering blind {!! !!} output.
- What are the best Laravel alternatives to victoire/html-widget?
- Build the behavior natively: a migration and model, an authorization policy, a Blade component, and a maintained sanitizer such as mews/purifier or symfony/html-sanitizer. For CMS-style blocks, use a Laravel-native content block package or a vetted Blade component library. The value is the reusable content pattern, not this Symfony bundle.
- How do I migrate Victoire HTML widget content to Laravel?
- Export the widget HTML and metadata from Victoire, then seed it into an application-owned table with author and timestamp fields. Rebuild rendering as a Blade component and sanitize content on save or render. Carry the content, not the bundle or its Symfony dependencies.
- Does victoire/html-widget have tests, a license, or documentation?
- The technical evaluation reports no clear license, test, or coverage signal and no evidence of maintained documentation. That is a governance risk before it is a code risk. For production Laravel use, require those signals from any dependency you adopt.
Weaver
How can I help you explore Laravel packages today?