Removing need for custom scripts in tools/ dir? about react-slingshot HOT 3 CLOSED

Even if it were possible to completely configure browsersync on the command line, it would be a very long command. What do you feel is the downside of calling a separate script in tools?

from react-slingshot.

One potential downside is having to maintain the custom scripts as dev-stack and APIs evolve; in general I prefer to "own" as little code as possible and rely on packages maintained by others.

That being said, I think the current state of webpack/react/redux tooling is such that a lot of customization is required, and custom scripts are very flexible. It seems like this is necessary complexity ;) Closing.

from react-slingshot.

To clarify, there's nothing more "custom" about the js-based configuration file in /tools than a comparable Gulp config. In fact, if you check browsersync's docs, you'll see that I copy and pasted their recommended config largely verbatim. If I were using Gulp, I'd likely copy/paste from some gulp plugin doc.

from react-slingshot.