WIP: this is the work in progress branch of the upcoming vue-cli 3.0. Only for preview for template maintainers.

This project uses a monorepo setup that requires using Yarn because it relies on Yarn workspaces.

# install dependencies
yarn

# link `vue` executable
cd packages/@vue/cli
yarn link

# create test projects in /packages/test
export VUE_CLI_DEBUG=true # necessary for manual tests to work
cd -
cd packages/test
vue create test-app
cd test-app
yarn dev

There are two major parts of the system:

• @vue/cli: globally installed, exposes the vue create <app> command;
• @vue/cli-service: locally installed, exposes the vue-cli-service commands.

Both utilize a plugin-based architecture.

Creator is the class created when invoking vue create <app>. Responsible for prompting for preferences, invoking generators and installing dependencies.

Service is the class created when invoking vue-cli-service <command> [...args]. Responsible for managing the internal webpack configuration, and exposes commands for serving and building the project.

Plugins are locally installed into the project as devDependencies. @vue/cli-service's built-in commands and config modules are also all implemented as plugins. This repo also contains a number of plugins that are published as individual packages.

A plugin should export a function which receives two arguments:

• A PluginAPI instance
• Project local options specified in vue.config.js, or in the "vue-cli" field in package.json.

The API allows plugins to extend/modify the internal webpack config for different environments and inject additional commands to vue-cli-service. Example:

module.exports = (api, projectOptions) => {
  api.chainWebpack(webpackConfig => {
    // modify webpack config with webpack-chain
  })

  api.configureWepback(webpackConfig => {
    // modify webpack config
    // or return object to be merged with webpack-merge
  })

  api.regsiterCommand('test', args => {
    // register `vue-cli-service test`
  })
}

A plugin published as a package can also contain a generator.js file or a generator directory with index.js. The generator inside a plugin will be invoked after the plugin is installed.

A generator should export a function which receives a GeneratorAPI instance as the only argument. The API allows a generator to inject additional dependencies or fields into package.json and add files to the project. Example:

module.exports = (api, options) => {
  api.extendPackage({
    scripts: {
      test: 'vue-cli-service test'
    }
  })

  api.render('./template')
}

A plugin with a generator that injects additional dependencies other than packages in this repo (e.g. chai is conditionally injected by @vue/cli-plugin-unit-mocha-webpack/generator/index.js) should have those dependencies listed in its "devDependencies" field. This ensures that the package always exist in this repo's root node_modules so that we don't have to reinstall them on every test.