A Guard plugin that automatically reloads your browser when view files are modified during development.
Guard::LiveReload is a Ruby gem that automatically reloads web browsers when view files are modified during development. It integrates with the Guard file watcher system to monitor changes to templates, stylesheets, JavaScript files, and other view assets, then triggers browser refresh without manual intervention. This solves the problem of constantly switching between editor and browser to see changes during frontend development.
Ruby developers working on web applications, particularly those using Rails or Rack-based frameworks who want to streamline their frontend development workflow. It's especially useful for developers frequently modifying HTML templates, CSS, or JavaScript files.
Developers choose Guard::LiveReload because it integrates seamlessly with the popular Guard ecosystem, requires minimal configuration, and eliminates the repetitive task of manual browser refreshing. Its flexibility in file pattern matching and compatibility with LiveReload browser extensions make it a reliable choice for automated development workflows.
Guard::LiveReload automatically reload your browser when 'view' files are modified.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates directly with Guard's file watching system, allowing easy setup via 'guard init livereload' command and leveraging Guard's ecosystem for consistent workflows.
Configurable watch patterns in Guardfile support various file types like ERB, HAML, Slim, CSS, and JS, enabling tailored monitoring for complex project structures.
Compatible with LiveReload extensions for Safari, Chrome, and Firefox, allowing automatic reloads without additional server-side injection in supported browsers.
Works well with rack-livereload for Rails and Rack-based apps, providing seamless integration for common Ruby web frameworks as noted in the usage section.
The README warns of past security vulnerabilities requiring updates, and the project is seeking a new maintainer, indicating potential instability and slower fixes.
Requires Guard to be installed separately and configuration of both Gemfile and Guardfile, adding complexity compared to standalone or modern dev server tools.
Tied to Ruby and Rack-based applications, making it unsuitable for projects outside this stack without significant workarounds or alternative solutions.