Well I was able to debug output from browsersync-webpack-plugin - not to be confused with browser-sync-webpack-plugin . I did this by adding
NODE_DEBUG=browsersyncwebpackplugin to the
start script, but it dumps out so much information I can't really get anything meaningful out of it.
It kind of feels like this plugin (although obviously useful) is obfuscating the build process. Webpack is already pretty complex, without having to dig further into a plugin to debug things. I'm not trying to dish on QWp6t's hard work, but I feel like with all the build code we already have, what is another ~50-100 lines to accomplish this in a way where can actually see an interact with what is going on, rather than delegate to a plugin?
All that aside, file changes are definitely being detected, I am getting debug info dumped out every time I save a blade file, just not HTML injection. I have ripped everything out of my templates directory trying to get to a simplest case, and I'm still coming up short.
EDIT: I AM AN IDIOT!
I forgot to disable hypercache on the site I was working on. Since the page is cached, bs-html-injector cannot detect any changes to the HTML. DUH.