New install of Sage 9. OS Mac Mojave. Installation went fine. When I make any changes to either a _sccs file or a blade template the changes are not reflected in the browser. There are no errors displayed, also not in Developer’s Console. The message “Browsersync Connected” does appear, but I nev…

I had similar symptoms, in that case it was CORS, maybe this discussion is useful: [image] Sage 9 + BrowserSync not loading any CSS at all on 'yarn run start' sage @Simeon : Edit: According to author BrowserSync has to be configured with advanced key: new BrowserSyncP…

I tried that too. Did not help. Config.json: { “entry”: { “main”: [ “./scripts/main.js”, “./styles/main.scss” ], “customizer”: [ “./scripts/customizer.js” ] }, “headers”: { “Access-Control-Allow-Origin”: “" }, “publicPath”: “/wp-content/themes/tech2protect”, “devUrl”: “ http://www.mydom…

So there are no notices, warnings or errors in Developer Console when the page loads or BrowserSync loads styles? But when you save a SCSS asset file, BrowserSync shows a reloading mesage on the page? Have you tried ‘obvious’ styles like * {display: none; } in main.scss?

There are no warnings or errors at all. The _sccs files do get compiled, because if I make an error in them I see the error in the console during compile. The updates just don’t seem to arrive at the browser. Tried different browsers as well. “Browsersync: connected” message is appearing all the …

And it is both css and blade-templates that are not syncing.

Never got it to work, but was able to at least get my files compiled and save to disk so I can work thanks to: [image] Issue: Enable CSS build when watching opened by nicooprat on 2017-02-01 closed by retlehs on 2017-02-01 Submit a feature request or bug report I've rea…

You have a configuration issue with your devUrl and/or proxyUrl - should be able to get that sorted so you can use the build process as intended

What problem do I have with devURL and proxyurl? Site opened fine on localhost:3000. Just never updated.

Looks like your devURL is pointing to a live production website and not your local environment maybe? If not, it could be the config URLs. I just had a problem with the config.json URLs and had to include the subfolder of the devURL to the proxyURL. Check this post for fixes: [image] …

I do not have a local environment. I develop straight on the server. So the solution I have right now is working.

Browsersync not syncing

sage

strarsis March 9, 2019, 12:13am 2

I had similar symptoms, in that case it was CORS, maybe this discussion is useful: