You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An optional audible bell, either in Terminal, or browser, when live/hot -reload is triggered. In-browser preferred as it's the last part of the live/hot reload daisy-chain and therefore would give more contextual information about the operation of hot/live reloading.
Feature Use Case
I'll be using "HTML theming" to describe the application of stylesheets, scripts and other resources to HTML documents.
When IT-professionals with differing specializations collaborate together on HTML document theming, their workflows and requirements towards a build/development environment may differ. Many tools concerned with HTML theming are optimized for a multi-monitor setup and graphical IDEs. I don't see why that should become canon.
Of course, it is advisable to use a multi-monitor setup for certain tasks, such as where CSS media queries become relevant during development, but that's a small fraction of the overall development work.
In order to verify that live/hot reload has been triggered, you currently need to check the logs of the webpack serve terminal command output and you need to see a browser window indicating a reload in order to verify that a watched file actually triggered a change, and is applied to the served HTML document. Without a multi-monitor setup, this becomes very tedious for no reason, since I need to take the extra window-switching into account, as terminal and browser window are not side-by-side, when verifying the logs have changed and browser window reloaded.
The text was updated successfully, but these errors were encountered:
Feature Proposal
An optional audible bell, either in Terminal, or browser, when live/hot -reload is triggered. In-browser preferred as it's the last part of the live/hot reload daisy-chain and therefore would give more contextual information about the operation of hot/live reloading.
Feature Use Case
I'll be using "HTML theming" to describe the application of stylesheets, scripts and other resources to HTML documents.
When IT-professionals with differing specializations collaborate together on HTML document theming, their workflows and requirements towards a build/development environment may differ. Many tools concerned with HTML theming are optimized for a multi-monitor setup and graphical IDEs. I don't see why that should become canon.
Of course, it is advisable to use a multi-monitor setup for certain tasks, such as where CSS media queries become relevant during development, but that's a small fraction of the overall development work.
In order to verify that live/hot reload has been triggered, you currently need to check the logs of the
webpack serve
terminal command output and you need to see a browser window indicating a reload in order to verify that a watched file actually triggered a change, and is applied to the served HTML document. Without a multi-monitor setup, this becomes very tedious for no reason, since I need to take the extra window-switching into account, as terminal and browser window are not side-by-side, when verifying the logs have changed and browser window reloaded.The text was updated successfully, but these errors were encountered: