Repository navigation
Browser Sync #312
Unanswered
christianthibault
asked this question in
Q&A
Replies: 3 comments 5 replies
|
Try |
2 replies
|
Setting up the child theme is indeed easier than before. But the way the files are now compiled takes much longer than the gulp command. Often more than 2 seconds. Over a day of work, it adds up. Is there a way to speed up the process? |
1 reply
|
I can't seem to find any documentation that speaks on how to use browser-sync with a site that is https:// .. I noticed that when I put the domain in the proxy it automatically adds the http:// prefix. Couldn't find anywhere to point to my local development certificates or keys. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I used to launch gulp watch-bs (Browser Sync) while developing to avoid refreshing after each modification to Understrap Child.
I downloaded the latest version, followed the instructions, modified the proxy value of src/build/browser-sync.config.js to my MAMP local URL, launched npm run watch. CSS files are compiled upon saving _src/sass/theme/child_theme.scss, but it does not launch a synchronized browser window. Why?
Thank you,
Christian Thibault
All reactions