From cb6ed2872a927a5b520143c07ff3d8d267ed243a Mon Sep 17 00:00:00 2001 From: Laurence de Bruxelles Date: Fri, 29 Apr 2022 16:32:18 +0100 Subject: [PATCH] Add comment clarifying that Browser Sync is only for local development Browser Sync doesn't play well with Glitch, so now it won't run if your prototype is on Glitch, even if you have `useBrowserSync: true` in your config file. I think this shouldn't actually affect users, because using Browser Sync with Glitch doesn't make much sense (it won't work, and Glitch auto-relaods for you anyway), but this commit adds a comment anyway to make it clear that Browser Sync is only used for development environments (the config variable has always been ignored when NODE_ENV is true). --- app/config.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/config.js b/app/config.js index 465da27d00..92fb90007d 100644 --- a/app/config.js +++ b/app/config.js @@ -25,7 +25,7 @@ module.exports = { // Force HTTP to redirect to HTTPS on production useHttps: 'true', - // Enable or disable Browser Sync + // Enable or disable Browser Sync (local development only) useBrowserSync: 'true' }