Does the vue webpack template (via vue-cli) become easier to use later on?
<h3>Background</h3>
<p>Starting on a new vue.js (2.0) project. I've worked with <code>vue-cli</code> in other projects (<a href="https://github.com/vuejs-templates/webpack" rel="noreferrer">vuejs-templates/webpack</a>) and found the build process difficult to grasp when doing any kind of changes.
On top of that, webpack is infamous for its lacking documentation, therefore it turned out to be a lot of work even to achieve minor tweaks to the build process.
In general, I believe I understand both webpack and vue-loader. I'm still having a hard time getting the full picture of <code>vuejs-templates/webpack</code> though.</p>
<h3>Question</h3>
<p>I'm considering rolling my own webpack config for this app, but I'm concerned I'll eventually end up with a build process as big as the current <code>vuejs-templates/webpack</code>.
My plan was to work my way up from <a href="https://github.com/vuejs-templates/webpack-simple/tree/master/template" rel="noreferrer">vuejs-templates/webpack-simple</a> and not overcomplicate things too much.
What I have in mind is a config / build process situated somewhere in between <code>vuejs-templates/webpack-simple</code> and <code>vuejs-templates/webpack</code>.</p>
<p>I'm interested to see how others (with perhaps more experience that I have) feel about <code>vuejs-templates/webpack</code>. Wonder if it will just get harder to use as the project grows or if it will all make sense eventually.</p>
<p><strong>Does it make sense to roll my own webpack config / build process or should I just suck it up and use <code>vuejs-templates/webpack</code>?</strong></p>