Go to file

Eduardo San Martin Morote 412ec86128 fix(types): export missing types from runtime-core (#889 )		2020-03-27 09:30:49 -04:00
.circleci	build: run ls-lint on commit	2020-03-19 16:38:31 -04:00
.github	build: make @vue/shared public	2020-02-29 22:04:42 -05:00
.vscode	workflow: support debug single jest test file in vscode (#360 )	2019-10-23 11:20:05 -04:00
packages	fix(types): export missing types from runtime-core (#889 )	2020-03-27 09:30:49 -04:00
scripts	build: tweak flags	2020-03-24 17:57:27 -04:00
test-dts	refactor(runtime-core): revert setup() result reactive conversion	2020-02-26 19:01:42 -05: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	chore: config comments	2019-09-03 12:17:33 -04:00
CHANGELOG.md	release: v3.0.0-alpha.10	2020-03-24 18:33:40 -04:00
jest.config.js	build: avoid runtime wildcard import in global build	2020-02-13 18:50:36 -05:00
LICENSE	chore: license	2019-10-28 11:15:17 -04:00
package.json	build: enforce node version on install (#881 )	2020-03-25 09:44:19 -04:00
README.md	chore: readme [ci skip]	2020-03-24 18:39:08 -04:00
rollup.config.js	build: tweak flags	2020-03-24 17:57:27 -04:00
tsconfig.json	refactor(types): use stricter settings	2020-03-23 11:08:22 -04:00
yarn.lock	build(deps): bump @babel/parser from 7.9.3 to 7.9.4 (#880 )	2020-03-25 09:30:19 -04:00

README.md

vue-next

Status: Alpha.

The current codebase has reached feature parity with v2.x (except for features explicitly removed by RFCs), and has landed all the changes proposed in merged RFCs. We are ready to advance to beta phase once we resolve a number of pending RFCs.

There is a simple 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).

Known Issues

There is currently no way to attach custom instance properties via Vue.prototype.
The current implementation requires native ES2015+ in the runtime environment and does not support IE11 (yet).

Contribution

See Contributing Guide.