Enhancing 'gowebly run' for Seamless Browser Synchronization

[abuffery]

Problem Statement:

The current 'gowebly run' command in our web development workflow watches for changes in Templ files and Tailwind CSS, but it lacks automatic browser synchronization. Developers are required to perform additional manual steps, including stopping 'gowebly run,' restarting it, and refreshing the browser to view the changes. This process disrupts the development flow and lacks the smooth, instantaneous feedback seen in modern frontend frameworks with hot reload functionality.

Proposal:

To enhance the 'gowebly run' command to provide a seamless development experience similar to hot reload in frontend frameworks. By implementing automatic browser synchronization, we can significantly improve the efficiency and user experience for developers.

Key Features:

1. Real-Time Synchronization:

   • 'gowebly run' will continuously monitor Templ files and Tailwind CSS.
   • As soon as a change is detected, it will trigger an automatic refresh in the connected browser, ensuring that the latest changes are immediately visible.

2. Streamlined Development Workflow:

   • Eliminate the need for manual steps such as stopping, restarting, and refreshing.
   • Developers can focus on coding while enjoying a responsive and dynamic development environment.

3. Configuration Options:

   • Provide configurable settings for automatic synchronization, allowing developers to enable or disable this feature as needed.
   • Offer options for fine-tuning synchronization behavior, ensuring flexibility for different project requirements.

Benefits:

• Improved Developer Productivity: Developers can iterate faster and see changes in real-time, reducing context-switching and wait times.
• Enhanced User Experience: A seamless development environment leads to a more enjoyable and efficient coding experience.
• Competitive Advantage: Offering a feature akin to hot reload aligns our tool with modern development expectations.

Implementation Considerations:

• Ensure cross-browser compatibility.
• Handle edge cases gracefully, such as large-scale projects or complex dependencies.

Rollout Plan:

1. Begin with internal testing to iron out any issues and gather feedback.
2. Release a beta version to a select group of users or projects for further testing and evaluation.
3. Gradually roll out the enhanced 'gowebly run' to all users, accompanied by documentation and support resources.

Conclusion:

Enhancing the 'gowebly run' command to provide automatic browser synchronization would significantly elevate the development experience for users. This feature would allow gowebly to compete with industry standards found in frontend that empowers developers to work more efficiently and effectively.

[JGabrielGruber]

I agree with @abuffery here, it would make the tool much more appealing;

My suggestions is to turn this into an Feature Request Issue, so it can be more easily traceable the progress of it, and allowing others community members to help.

I would like to help with this, sure I don't have the experience writing Golang applications, but I believe that with the vision from @koddr of how it should be, it would be easier to collaborate.

[koddr]

Thanks, @abuffery and @JGabrielGruber

Starting with v2.0.0, the Gowebly CLI uses Air (air) as a live-reloading tool for continuous development. It covers the live-reloading needs for both frontend and backend.

If there are any other comments on live-reloading mode, I'd love to hear them! 😊

[JGabrielGruber]

Let's goo!!!

Nice work, @koddr
I'll be trying that on a side project

[JGabrielGruber]

@koddr it works like a charm!! Very Perfect!!!! I'm very glad with the addition
I hope to soon™ to improve the AUR package and include the Air dependency