You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Eduardo San Martin Morote 412ec86128
fix(types): export missing types from runtime-core (#889)
5 years ago
.circleci build: run ls-lint on commit 5 years ago
.github build: make @vue/shared public 5 years ago
.vscode workflow: support debug single jest test file in vscode (#360) 6 years ago
packages fix(types): export missing types from runtime-core (#889) 5 years ago
scripts build: tweak flags 5 years ago
test-dts refactor(runtime-core): revert setup() result reactive conversion 6 years ago
.gitignore chore: add the yarn error log file to git ignore (#150) 6 years ago
.ls-lint.yml fix(types): export missing types from runtime-core (#889) 5 years ago
.prettierrc init (graduate from prototype) 7 years ago
CHANGELOG.md release: v3.0.0-alpha.10 5 years ago
LICENSE chore: license 6 years ago
README.md chore: readme [ci skip] 5 years ago
api-extractor.json chore: config comments 6 years ago
jest.config.js build: avoid runtime wildcard import in global build 6 years ago
package.json build: enforce node version on install (#881) 5 years ago
rollup.config.js build: tweak flags 5 years ago
tsconfig.json refactor(types): use stricter settings 5 years ago
yarn.lock build(deps): bump @babel/parser from 7.9.3 to 7.9.4 (#880) 5 years ago

README.md

vue-next CircleCI

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.