Go to file
2020-07-06 18:56:21 -04:00
.circleci test: run tests with --runInBand by default 2020-07-01 16:18:39 -04:00
.github chore: adjust yarn warning [ci skip] 2020-06-09 17:39:48 -04:00
.vscode workflow: cross platform vscode jest debugging (#414) 2020-06-12 10:34:31 -04:00
packages chore: warn NaN vnode key 2020-07-06 18:56:21 -04:00
scripts chore: remove unnecessary flag in release script 2020-07-01 20:59:11 -04:00
test-dts fix(types): should unwrap array -> object -> ref 2020-06-29 12:26:28 -04:00
.eslintrc.js fix(types): should unwrap array -> object -> ref 2020-06-29 12:26:28 -04:00
.gitignore chore: add the yarn error log file to git ignore (#150) 2019-10-09 12:13:54 -04:00
.ls-lint.yml fix(types): export missing types from runtime-core (#889) 2020-03-27 09:30:49 -04:00
.prettierrc init (graduate from prototype) 2018-09-19 11:35:38 -04:00
api-extractor.json feat(types): adjust type exports for manual render function and tooling usage 2020-06-10 14:57:21 -04:00
CHANGELOG.md release: v3.0.0-beta.18 2020-07-01 21:06:25 -04:00
jest.config.js chore: ignore unreachable files from coverage 2020-06-11 17:14:11 -04:00
LICENSE chore: license 2019-10-28 11:15:17 -04:00
package.json release: v3.0.0-beta.18 2020-07-01 21:06:25 -04:00
README.md chore: fix link in readme (#1501) 2020-07-04 10:11:54 +02:00
rollup.config.js build(deps): bump build deps 2020-06-16 12:09:20 -04:00
tsconfig.json chore: remove unnecessary path in tsconfig.json 2020-05-01 16:21:48 -04:00
yarn.lock build(deps): bump csstype from 2.6.10 to 2.6.11 (#1487) 2020-07-06 15:57:11 -04:00

vue-next beta CircleCI

Status: Beta

  • All planned RFCs have been merged.

  • All merged RFCs have been implemented.

  • Vue CLI now has experimental support via vue-cli-plugin-vue-next.

  • There is also a simple plain webpack-based setup with Single-File Component support available here.

Please note that there could still be undocumented behavior inconsistencies with 2.x. When you run into such a case, please make sure to first check if the behavior difference has already been proposed in an existing RFC. If the inconsistency is not part of an RFC, then it's likely unintended, and an issue should be opened (please make sure to use the issue helper when opening new issues).

In addition, the current implementation requires native ES2015+ in the runtime environment and does not support IE11 (yet). The IE11 compatible build will be worked on after we have reached RC stage.

Status of the rest of the framework

Vue Router

We still have a few minor router hook behavior consistency issues with vue-router@3.x, but these are the only things that is blocking the router from being marked as Beta. The router is usable for new, non-critical projects.

Vuex

The only difference between Vuex 4.0 and 3.x is that it's Vue 3 compatible! It is ready to enter RC together with Vue 3 core.

Vue CLI

Vue 3 support in Vue CLI is currently provided via the vue-cli-plugin-vue-next plugin. You can scaffold a new project and then run vue add vue-next to switch to Vue 3. Vue 3 will become a option in the project creation process when it reaches RC.

Note if you are not particularly attached to webpack and IE11 support, you can also start a Vue 3 project with Vite.

JSX Support

There are currently two JSX transform implementations for Vue 3 with slightly differing syntax (for Vue specific features):

We are using this thread to unify the design and land on an official specification of how Vue features should be handled in JSX. If you use Vue with JSX, please provide your feedback in that thread.

Other Projects

Project Status
vue-devtools WIP (beta channel with Vue 3 support in early July)
eslint-plugin-vue alpha [Github]
@vue/test-utils alpha [Github]
vue-class-component alpha [Github]
vue-loader alpha [Github]
rollup-plugin-vue alpha [Github]

Contribution

See Contributing Guide.