Webpack-dev-server as a "runner" for tests and eslint?
<p>I have webpack-dev-server, and I run it from npm (package.jso)n:</p>

<pre><code>"scripts": {
    "build": "NODE_ENV=production webpack -p --config webpack.production.config.js --progress --profile --colors",
    "dev": "webpack-dev-server --progress --profile --colors --hot"
},
</code></pre>

<p>It is from some starter kit and it works well. I can run <code>node run dev</code> and webpack watches any changes in my files and reloads modules.</p>

<p>That is fine.</p>

<p>But! I've worked with gulp recently and my workflow was:
0. Start <code>gulp watch</code>.
1. Make awesome change in any .js file.
2. Gulp runs bundler (browserify), eslint and tests (karma and jasmine on phantomjs) on every change.</p>

<p>Is it possible to achieve that flow with webpack-dev-server? Or should I rather use webpack with "watch" flag as one of tasks in gulp (instead of browserify) and stay with my flow?</p>

<p>I think that I don't really need this hot module reloading thing. I have never worked with that and I was fine (well, it is not very solid argument, but still... :)). It is really that super feature, and I should run webpack-dev-server and maybe gulp tasks in separate terminal window?</p>

<p>Any ideas?</p>