Weave Code
Code Bundle Laravel Package
liip/code-bundle
LiipCodeBundle is a Symfony bundle for displaying and editing source code in your apps. It adds syntax highlighting and code-editor integration, making it easy to embed readable code snippets in templates, documentation, and admin screens.
Liip Code Bundle
Frequently asked questions about Code Bundle
- Does liip/code-bundle work with Laravel?
- No. It is a Symfony2 bundle built around Symfony's Bundle interface, DI container, and logical-name notation, none of which exist in Laravel's boot path. Installing it in a Laravel app will fail Composer dependency resolution rather than provide usable Artisan commands. The package is also deprecated and archived, so there is no Laravel support to expect.
- Can I install liip/code-bundle in Laravel 10 or 11?
- Not practically. Laravel 8–11 pin Symfony 5/6/7 console and related components, while liip/code-bundle requires Symfony 2.x-era APIs. Composer will typically reject the install because of those constraints. Even a forced install would leave the bundle without a Symfony kernel to introspect.
- What does liip/code-bundle actually do?
- It was a Symfony2 code-generation and code-navigation bundle. It provided command-line generators and template-driven scaffolding, and could resolve Symfony logical names such as AcmeDemoBundle:Default:index to bundle, template, or service paths. It fit Symfony's bundle and container conventions rather than Laravel's.
- Is liip/code-bundle still maintained?
- No. The repository is marked DEPRECATED and archived, with the last release on 2015-06-15, about 25 stars, zero dependents, and no active maintainer. There are no future patches or security updates. Treat it as historical reference only.
- What Symfony version does liip/code-bundle require?
- It targets Symfony 2.x and uses APIs that were removed in Symfony 3 and 4, including older command definition signatures and container get() semantics. That is why it cannot coexist with the Symfony 5/6/7 components used by modern Laravel. It is not a Symfony 5+ bundle.
- Why does Composer fail when installing liip/code-bundle with Laravel?
- Composer fails because the bundle's Symfony 2.x console, DI, and HttpKernel constraints conflict with the Symfony 5/6/7 components Laravel 8–11 require. The conflict is architectural, not a missing flag or autoload tweak. Forcing the install would not produce a working bundle because Laravel has no Symfony bundle registry or kernel.
- What should I use in Laravel instead of liip/code-bundle?
- Use Laravel-native tooling. php artisan about, IDE go-to-class, ReflectionClass::getFileName() in Tinker, app()->getBindings() and getLoadedProviders() cover most service and class introspection, and view()->getFinder()->find() resolves view paths. For editor integration and autocompletion, use your IDE, spatie/laravel-ignition stack-trace links, and barryvdh/laravel-ide-helper.
- Can I fork liip/code-bundle to work with Laravel?
- You can, but it is a rewrite rather than a port. A viable version would reimplement the same ergonomics as Artisan commands against Laravel primitives such as bootstrap/cache/packages.php, the container bindings, loaded providers, and ReflectionClass. That is roughly 200–400 lines and creates an internal package you must own indefinitely. Greenfield Artisan commands are usually cheaper.
- Is liip/code-bundle safe to run in production?
- It is not suitable for production in a Laravel app, and it is abandoned even for its original Symfony2 context. The old code targets PHP 5.3-era idioms and Symfony2 APIs and would likely surface deprecation or dynamic-property errors on PHP 8.x. Its editor-launch commands also shell out to hardcoded binaries like subl, mate, and vim using string interpolation, which is unportable and a mild command-injection risk if input is not escaped.
- How do I find a class or view path in Laravel like liip/code-bundle did in Symfony?
- Use Laravel's own reflection and filesystem APIs. ReflectionClass::getFileName() returns a class file path, view()->getFinder()->find('name') resolves a view, and app()->getBindings() or getLoadedProviders() lists container services and providers. Wrap those in a small Artisan command group such as code:find-class or code:find-view if you want the old muscle memory. That gives you the capability without the abandoned Symfony2 dependency.
Weaver
How can I help you explore Laravel packages today?