Haoqun Jiang 044f5b3b7e refactor: use a version map to determine the newest dependency versions
Now that lerna independent mode is used to release new versions, we can
no longer ensure the core service/plugin versions are in sync with
@vue/cli itself. So `vue-cli-version-marker` is now used to store the
latest version map of core packages.

In order to automate this process, all the core cli packages are listed
as `devDependencies` of `vue-cli-version-marker`. This will cause a
cyclic dependency warning in lerna bootstrap, and that warning can be
safely ignored because these are just `devDependencies` which won't
affect end users.

Another gotcha is that the version of `vue-cli-version-marker` will be
bumped each time we do a release. This may break the remote version
check logic before rc.12 (due to
1ae223dfc0 (diff-ac5fc3f8b11df9fc948b8e5aa52a074e)
the background version check might never get executed since rc.12)
2018-11-12 14:24:41 +08:00
2018-07-13 11:47:46 -04:00
2018-07-13 10:56:22 -04:00
2018-01-06 13:04:43 -05:00
2018-11-01 14:14:07 +08:00
2018-08-10 11:12:48 -04:00
2018-11-02 23:06:07 +08:00

vue-cli Build Status Windows Build status

Vue CLI is the Standard Tooling for Vue.js Development.

Documentation

Docs are available at https://cli.vuejs.org/ - we are still working on refining it and contributions are welcome!

Contributing

Please see contributing guide.

License

MIT

Description
🛠️ webpack-based tooling for Vue.js Development
Readme MIT 45 MiB
Languages
JavaScript 75%
Vue 22.9%
TypeScript 0.9%
Stylus 0.5%
HTML 0.3%
Other 0.4%