Hot refresh
I understand that one of the disadvantages we have when working with TALL is that every change in a Blade template requires me to refresh the entire screen in the browser instead of using "Hot Module Replacement." This takes a few seconds with each change. Does anyone have any advice or practices so that every time I save, it doesn't result in a long wait and I can maintain an uninterrupted workflow? (Let’s understand that this is not a criticism of the stack, but rather a way to find a solution to a problem.)
1 Reply
I was unaware, but the key is to use this plugin:
https://github.com/defstudio/vite-livewire-plugin It boosts your productivity by 1000 times!
https://github.com/defstudio/vite-livewire-plugin It boosts your productivity by 1000 times!
GitHub
GitHub - defstudio/vite-livewire-plugin: Laravel Vite handler for L...
Laravel Vite handler for Livewire components. Contribute to defstudio/vite-livewire-plugin development by creating an account on GitHub.