Weave Code
Hello Bundle Laravel Package
liip/hello-bundle
LiipHelloBundle is a small Symfony bundle providing a simple Hello World example with controller, routing, and template setup. It serves as a lightweight reference for learning Symfony bundle structure or testing basic app integration.
[DEPRECATED] Alternative Hello World Bundle for Symfony2 using several FriendsOfSymfony Bundles
Frequently asked questions about Hello Bundle
- Can I install liip/hello-bundle in a Laravel application?
- No, it is not viable as a runtime dependency in Laravel. It is a Symfony 2 bundle built around Bundle subclasses, DI extensions, XML/YAML service definitions, and Symfony routing, not Laravel service providers. Composer will conflict with modern Laravel's Symfony 6.x/7.x components, and the archived repository has no PHP 8.x compatibility.
- What is liip/hello-bundle used for?
- It was a minimal Symfony 2 Hello World bundle demonstrating how a controller, routing entry, Twig template, and configurable greeting message fit together. It is a reference application for bundle structure, not a reusable library with a versioned API surface. The package is marked deprecated and the repository is archived.
- Does liip/hello-bundle support Laravel 10, 11, or 12?
- No. It targets Symfony 2.x and an end-of-life PHP baseline, while Laravel 10, 11, and 12 require PHP 8.2+ and modern Symfony components. There is no adapter path because Laravel has no Symfony bundle kernel to register into. The framework mismatch is structural, not a simple configuration issue.
- How do I install and configure liip/hello-bundle?
- You cannot cleanly install it in a modern Laravel app. Composer resolution fails on symfony/* constraints before any class loads, and --ignore-platform-reqs only defers class-not-found fatals at kernel or bundle registration. In its original Symfony 2 context it was installed via Composer and configured through bundle settings for the greeting message.
- Is liip/hello-bundle maintained or safe for production?
- No. The package is deprecated, the repository is archived, and there is no maintainer for security response or PHP 8.x updates. Zero dependents and 198 historical stars reflect Symfony 2-era usage, not current production fitness. Forcing installation would drag abandoned transitive dependencies into your application.
- What is the Laravel alternative to liip/hello-bundle?
- Implement the pattern natively: one route in routes/web.php, one invokable controller, and one Blade view, roughly 50 lines with no external dependency. That keeps ownership in-house and avoids EOL framework baggage. If you need standardization, publish it as an internal Composer package under your own namespace and registry.
- Why does Composer fail when requiring liip/hello-bundle in Laravel?
- Laravel pulls Symfony 6.x/7.x components transitively, while this bundle requires Symfony 2.x constraints and abandoned FriendsOfSymfony packages. The dependency solver reports conflicts before any class loads. Bypassing it with --ignore-platform-reqs introduces abandoned packages that break when Symfony kernel classes are touched.
- Can I use only the routing or controller part of liip/hello-bundle?
- No. Its routing is Symfony routing and its controller depends on Symfony's HTTP kernel and bundle conventions, so there is no partial-adoption path into Laravel's router or container. The code is not portable piece by piece. Reimplement the hello endpoint natively on Laravel's routing and controller stack.
- Can I use liip/hello-bundle for testing or smoke tests in Laravel?
- Not reliably. The package is archived and incompatible with modern Laravel and PHP, so it cannot serve as a dependable smoke-test dependency. A health-check or hello endpoint is trivial to add as a native route and controller in Laravel. Use maintained Laravel testing tools such as PHPUnit or Pest instead.
- What should I do if liip/hello-bundle appears in my dependency intake list?
- Treat it as a tripwire example: EOL framework, archived repository, deprecated package, and zero dependents. Record a written rejection covering framework mismatch and maintenance risk, then close the intake item so it does not resurface. Frame the decision as already covered natively in about one day, not as having no option.
Weaver
How can I help you explore Laravel packages today?