I’m getting exactly the same error, but can’t seem to fix it.
Here are the steps that I have followed:
Updated to beta 2
Removed ‘node_modules’ folder
Run ‘yarn’
Run ‘yarn run start’
Files show up in terminal that have not been changed
BrowserSync see’s changes in assets folder (scss & js) but doesn’t inject new files. I can see it ticking in the top right corner.
I don’t see the error in the console that @ben referenced
Changes do not show up after native browser refresh
I’m not seeing the __WEBPACK_IMPORTED_MODULE_2__util_Router__[false] error. But for me the js/css was 404-ing in BrowserSync because of an eslint error that was not being displayed for some reason. Once i ran yarn build it printed the error for me. Then fixed it and ran yarn start again and all was good.
So seems like eslint errors aren’t getting communicated to browsersync, at least for me.
I’m up and running on Valet + bedrock + Sage Beta 2.
on https://bedrock-sagebeta.dev/ all works fine but on localhost:3000 I have ERR_CONNECTION_CLOSED.
This is my config.json
Besides the broken initial browsersync session and the asset size limit warning, this fix works for me. However in Google Chrome, localhost:3000 keeps on looping and reloading, in Safari this doesn’t happen. This started happening from the alpha 4 version.
I just want to confirm that this bug exists and even after spending a couple of hours, I didn’t manage to solve it which makes Beta.1 unusable (at least in my case). Previous Sage versions Alpha 1,2,3 and 4 works well.
Update:
Switching to beta2 branch solved my issues. I still have to make initial manual reload but later autoreloading works as expected.
I merged the new beta 2 in my project and it’s still not working entirely as expected…
In Safari it works fine now and it injects style & script changes, however I don’t see any changed files in my terminal anymore, is that default behaviour?
But in Chrome (55.0.2883.95), the page keeps reloading every second with a BrowserSync message saying connected to BrowserSync.
Username:sage Username$ yarn run start
yarn run v0.18.1
$ webpack --hide-modules --watch --config assets/build/webpack.config.js
Webpack is watching the files…
[BS] Proxying: http://example.dev
[BS] Access URLs:
----------------------------------
Local: http://localhost:3000
External: http://10.0.1.9:3000
----------------------------------
UI: http://localhost:3001
UI External: http://10.0.1.9:3001
----------------------------------
[BS] Watching files...
Would this have anything got to do with this Yarn warning i got when running ‘yarn’ initially …
fsevents@1.1.1: The platform “win32” is incompatible with this module" and incompatibility with “win32”
There’s some discourse about it this specific warning at https://github.com/yarnpkg/yarn/issues/1217 but would that have anything to do with why template changes are not displaying in the ‘yarn run start’ terminal?