Go to file

Evan You c35fea3d60 fix(runtime-core): condition for parent node check should be any different nodes fix #622		2020-01-16 16:21:37 -05:00
.circleci	ci: bust cache	2019-12-20 10:59:21 -05:00
.github	chore: fix typo in contributing guide (#589 )	2020-01-07 11:33:22 +01:00
.vscode	workflow: support debug single jest test file in vscode (#360 )	2019-10-23 11:20:05 -04:00
packages	fix(runtime-core): condition for parent node check should be any different nodes	2020-01-16 16:21:37 -05:00
scripts	chore: fix publish log [ci skip]	2020-01-13 17:53:54 -05:00
test-dts	fix(types): components options should accept components defined with defineComponent (#602 )	2020-01-13 17:12:45 -05:00
.gitignore	chore: add the yarn error log file to git ignore (#150 )	2019-10-09 12:13:54 -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.2	2020-01-13 17:44:30 -05:00
jest.config.js	ci: skip e2e tests on netlify coverage builds	2019-12-23 10:51:28 -05:00
LICENSE	chore: license	2019-10-28 11:15:17 -04:00
package.json	release: v3.0.0-alpha.2	2020-01-13 17:44:30 -05:00
README.md	chore: update readme [ci skip]	2020-01-02 18:40:43 -05:00
rollup.config.js	build: warn invalid format in build script	2019-12-22 11:56:09 -05:00
tsconfig.json	chore: Use dynamic paths in tsconfig.json (#548 )	2019-12-18 11:46:07 -05:00
yarn.lock	build(deps-dev): bump @types/jest from 24.0.25 to 24.9.0	2020-01-16 08:07:17 +00:00

README.md

vue-next

Status: Alpha.

The current codebase has basic feature parity with v2.x, together with the changes proposed in merged RFCs. There is a simple webpack-based setup with Single-File Component support available here.

At this stage, the only major work left is server-side rendering, which we are actively working on. In the meanwhile, we would like our users to start building small experimental apps using the alpha releases to help us identify bugs and stabilize the implementation.

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.