Weave Code
Live Reload Bundle Laravel Package
kunstmaan/live-reload-bundle
Symfony bundle that adds automatic live reload to development: it watches templates, assets and config, then refreshes the browser when files change, so updates appear instantly without manual reloads. Handy for Kunstmaan CMS projects.
Kunstmaan Live Reload Bundle
A Symfony bundle that adds LiveReload support to development by automatically injecting the LiveReload client script into HTML responses. It keeps browsers in sync with asset changes, so CSS, JavaScript, and template updates appear without manual refreshes, while production responses stay untouched.
- Seamless Symfony integration via Composer and bundle registration
- Injects livereload.js into development HTML responses
- Configurable host and port for the LiveReload server
- Debug-only activation to avoid production overhead
- Works with common asset watchers and build tools
Frequently asked questions about Live Reload Bundle
- What is kunstmaan/live-reload-bundle?
- It is a Symfony 2.x bundle, Kunstmaan\LiveReloadBundle, that injects a LiveReload script tag into rendered HTML so the browser refreshes when templates, styles, or assets change. It is a read-only subtree split of the KunstmaanBundlesCMS monorepo, not a Laravel package. The only runtime behavior is emitting a script reference to localhost:35729/livereload.js, normally in development.
- Can I install kunstmaan/live-reload-bundle in a Laravel app?
- No, not as a supported path. The package relies on Symfony bundle registration, the DI container, and kernel events, none of which Laravel provides. Composer-installing it would pull Symfony HTTP kernel contracts without giving you a working Laravel integration.
- Does Kunstmaan LiveReloadBundle support Laravel 10 or Laravel 11?
- No. It targets Symfony 2.x and the PHP 5.4–5.6 era, and it has no service provider, middleware, or Blade integration for Laravel 10 or 11. Modern Laravel versions expect PHP 8.1+ and PSR-4 autoloading, which this package does not declare or verify.
- Is kunstmaan/live-reload-bundle maintained?
- No. Its last release was 2014-08-13, it has about 22 stars and zero dependents, and there is no active maintenance or CVE response path. That makes it a poor dependency for any current PHP project.
- What should Laravel developers use instead of LiveReloadBundle for hot reload?
- Use Laravel's native Vite integration, which ships with laravel/vite-plugin and provides HMR plus full-page reload for Blade changes via npm run dev. Projects still on Laravel Mix can use mix.browserSync() or Browsersync. These are maintained, bundler-native tools that fit Laravel's front-end workflow.
- How do I add LiveReload script injection to Laravel without this package?
- Write a small middleware that appends a script tag before the closing body tag on HTML responses, and register it only when app()->environment('local'). Gate the host and port through config rather than hard-coding localhost:35729. This is roughly 15 lines and avoids a framework-mismatched dependency.
- What PHP versions does kunstmaan/live-reload-bundle support?
- It was written for PHP 5.4 through 5.6 with Symfony 2.x. It is unverified against PHP 8.2 or 8.3 and may fatal on removed APIs, dynamic property deprecations, or stricter type handling. Do not assume PHP 8 compatibility.
- Is it safe to use LiveReloadBundle in production?
- No. The injected script points at a local development server, so if environment gating is misconfigured it can leak into staging or production and cause broken or mixed-content requests for real users. The package also has no maintained release or security response process. Keep any live-reload injection strictly local.
- Does kunstmaan/live-reload-bundle work with Vite or webpack?
- No. It assumes the legacy grunt-contrib-watch workflow and simply emits a livereload.js script tag. It has no integration with Vite HMR, webpack-dev-server, or modern Laravel bundlers.
- Should I fork kunstmaan/live-reload-bundle for Laravel?
- A fork is technically possible but not justified. You would strip the Symfony bundle plumbing and reimplement the behavior as a Laravel service provider plus response middleware, which is simpler to write in-house. If you do port it, the minimum bar is PHP 8.1+, Laravel 10 or 11, PSR-4 autoloading, and a composer.json that declares php and illuminate dependencies.
Weaver
How can I help you explore Laravel packages today?