title: Vuejs, Difficulties to build with relative path
body: <p>I'm facing difficulties to make a proper build with a relative path when I run <code>npm run build</code>. Resolving assets is easy but I don't know how to configure 2 things:</p>
  
  <p>1/ The <code>assetsPublicPath</code> in <code>config/index.js</code></p>
  
  <pre><code>// see http://vuejs-templates.github.io/webpack for documentation.
  var path = require('path')
  module.exports = {
    build: {
      env: require('./prod.env'),
      index: path.resolve(__dirname, '../dist/index.html'),
      assetsRoot: path.resolve(__dirname, '../dist'),
      assetsSubDirectory: 'static',
      assetsPublicPath: '/ONLY_ABSOLUTE_PATH_ARE_ALLOWED/',
      productionSourceMap: true,
      // Gzip off by default as many popular static hosts such as
      // Surge or Netlify already gzip all static assets for you.
      // Before setting to `true`, make sure to:
      // npm install --save-dev compression-webpack-plugin
      productionGzip: false,
      productionGzipExtensions: ['js', 'css']
    },
    dev: {
      env: require('./dev.env'),
      port: 8080,
      assetsSubDirectory: 'static',
      assetsPublicPath: '/',
      proxyTable: {},
      // CSS Sourcemaps off by default because relative paths are "buggy"
      // with this option, according to the CSS-Loader README
      // (https://github.com/webpack/css-loader#sourcemaps)
      // In our experience, they generally work as expected,
      // just be aware of this issue when enabling this option.
      cssSourceMap: false
    }
  }
  </code></pre>
  
  <p>2/ The <code>base</code> option in the <code>vue-router</code> config seems to accept only absolute path too...</p>
  
  <pre><code>const router = new VueRouter({
    mode: 'history',
    base: '/ABSOLUTE_PATH_ONLY/',
    routes: [
      { path: '/', redirect: '/fr/poster/home' },
      { path: '/:lang', redirect: '/:lang/poster/home' },
      {
        path: '/:lang/poster',
        component: PosterLayout,
        children: [
          {
            // UserProfile will be rendered inside User's &lt;router-view&gt;
            // when /user/:id/profile is matched
            name: 'home',
            path: 'home',
            component: Home
          },
          {
            // UserPosts will be rendered inside User's &lt;router-view&gt;
            // when /user/:id/posts is matched
            name: 'themeCover',
            path: ':theme',
            component: ThemeCover
          }
        ]
      },
      {
        name: 'themeDetails',
        path: '/:lang/theme/:theme',
        component: ThemeDetails
      }
    ]
  })
  </code></pre>
  
  <p>So, it works when I specified the correct future URL, but it's not "future proof" in case, the server is modified...</p>
  
  <p>Any ideas to solve this if it's solvable?</p>