cubicweb #13144391 Provide optionnal websocket driven reload mechanism for developping views [open]
Follow up of https://www.cubicweb.org/ticket/13144242
On some NPM dev environments, there exists a mechanism to improve the speed of code execution to browser by watching for file changes and then "pushing" the reload of a page in the browser (probably using websocket).
This should be optional obviously.
|done in||<not specified>|
|closed by||<not specified>|