From bc6fdf2bc96b9fa2e0b814bd57af3b758e6397f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Calvi=C3=B1o=20S=C3=A1nchez?= Date: Sun, 15 Sep 2024 22:04:23 +0200 Subject: [PATCH] fixup! feat(devsetup): Add step by step guide for a development setup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Daniel Calviño Sánchez --- docs/developer-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-setup.md b/docs/developer-setup.md index 80698cb309d..7e8e9d7b451 100644 --- a/docs/developer-setup.md +++ b/docs/developer-setup.md @@ -206,7 +206,7 @@ Note, however, that in some cases the watcher may stop running (for example, if Also note that both `make build-js` and `make watch-js` are just wrappers for `npm run dev` and `npm run watch`, so you could run those commands instead if they feel more familiar. -No matter if you manually rebuilt the JavaScript files or if you use the watcher note that you will need to force refresh Talk in the browser, as otherwise the previous version of the build JavaScript files could be cached and used instead of the latest one. +No matter if you manually rebuilt the JavaScript files or if you use the watcher note that you will need to force refresh Talk in the browser, as otherwise the previous version of the built JavaScript files could be cached and used instead of the latest one. Besides manually force refreshing the page you can disable the cache in the _Network_ tab of the developer tools of the browser, but keep in mind that it will only have effect if the developer tools are open (and the _Network_ tab might need to be open once after the developer tools were open, even if the cache was already disabled).