Is there a way to exclude vue.config.js from production output?

[gtbuchanan]

vue-cli-service build seems to include vue.config.js in the actual production output (Vue CLI v4.5.12). I assume it's included in Webpack for HMR in case it is changed during development. However, I wouldn't think there is a reason to include it in a production build considering there could be a bunch of code that would never be executed in a browser (e.g. chainWebpack). This has the undesirable effect of having any requires in vue.config.js included in my production output. For example, I'm using are-you-es5 to build transpileDependencies and it ends up in my app. The only workaround I could think of was to use browser-or-node and only load are-you-es5 when Node is detected:

const { isNode } = require('browser-or-node');
...
let transpileDependencies;
if (isNode) {
  // Reason: `eval` is used to prevent the lib from getting included in the production
  // package by webpack. Not sure why this happens or if there is a better way.
  // https://stackoverflow.com/a/41063795/1409101
  // eslint-disable-next-line no-eval
  const { checkModules } = eval('require')('are-you-es5');
  transpileDependencies = checkModules({
    path: '',
    checkAllNodeModules: false,
    ignoreBabelAndWebpackPackages: true
  }).es6Modules;
}

module.exports = {
  ...
  transpileDependencies,
  ...
};

Is there a way to prevent this?