plugin to extend options vue.config.js

What problem does this feature solve?

we have a plugin. This plugin will generate some data into vue.config.js when it is invoked. we can’t put this data into package.json, because it depend on some modules. for example:

const path = require('path')
module.exports = {
   css: {
      extract: true,
      loaderOptions: {
        stylus: {
          'resolve url': true,
          import:  [path.resolve(__dirname, './src/theme')]
        }
      }
    }
}

if we use api.render to generate vue.config.js, it can work. But if another plugin generate vue.config.js, the old vue.config.js will be overwrited.

What does the proposed API look like?

maybe like api.injectImports and api.injectRootOptions

[jawa-the-hutt]

@Akryum If it’s not recommended that we edit vue.config.js via a plugin initializing, what would be the recommended method to change the outputDir when a plugin initializes? Is there one, or would the user have to manually edit vue.config.js after the fact?

Specifically looking at making the outputDir dynamic based on the outcome of a conditional statement. Use case is regarding using the CLI 3 with NativeScript & Webpack and having the outputDir be determined by whether it is IOS or Android.

I have the rest of the templating worked out except for how to change the outputDir since we’re only supposed to change this in vue.config.js

[Akryum]

👍