-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: autostart browsersync by default #58
Comments
Personally, I usually only enable browsersync when I'm working on frontend of a site. To be honest, I find myself working more and more with Vite, which has auto-refresh, and thus replaces the need for browsersync completely. Would love to hear how often and prefered workflow for people that regulary use the addon. |
Closing. #60 reworked the docs and includes a "Auto-start the watcher server" section. There seems to be little call for "auto-start" to be the default. |
Thanks for maintaining this! There is in fact expectation of auto-start that we see doing support, but I think it's important to keep the default what you like it to be. |
I do hear some requests in discord and slack; hence #60 This issue was open for 3months with no feedback here so the issue was closed based on that. Happy to discuss here or else where. |
I think your approach is fine, and thanks for explaining how to do the auto-start in #60 |
In PR #56 , @rfay said
What are everyones opinions on this?
The text was updated successfully, but these errors were encountered: