I’ve got a project which relies heavily on gulp. A typical dev session would require only one command:
I’m ready to integrate Netlify Dev (/tree/netlify-dev), but trying to avoid introducing another command needed for a typical dev session:
That’s not that bad. I could deal with that. However…
Netlify Dev claims that it can do hot reloading, but it requires you to stream it to a live URL. I don’t need to do that with browsersync. I’m also not sure that they both reload in the same manner.
Additionally, I don’t think Netlify Dev can sync between multiple browsers/devices at the same time like browsersync does. This capability is extremely useful and I’d hate to see it go.
Do I need to ditch browsersync and just use gulp to watch for file changes, in two separate tabs? It’s bearable, but seems silly.
I’m open to all ideas, but I’m trying to avoid using any static site generators (for now). Thanks for reading.