Mirror
/
vuejs-vue-next
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
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.
1337 Commits
116 Branches
245 Tags
81 MiB
 
 
 
 
Tree: 52e4ac0727
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '52e4ac0727'
${ noResults }
Evan You 52e4ac0727
chore: fix changelog formatting [ci skip] 		6 years ago
.circleci ci: bust cache 6 years ago
.github chore: fix typo in contributing guide (#589) 6 years ago
.vscode workflow: support debug single jest test file in vscode (#360) 6 years ago
packages release: v3.0.0-alpha.3 6 years ago
scripts build: adjust release tag 6 years ago
test-dts types(reactivity): handle primitive + object intersection types in UnwrapRef (#614) 6 years ago
.gitignore chore: add the yarn error log file to git ignore (#150) 6 years ago
.prettierrc init (graduate from prototype) 7 years ago
CHANGELOG.md chore: fix changelog formatting [ci skip] 6 years ago
LICENSE chore: license 6 years ago
README.md chore: update readme [ci skip] 6 years ago
api-extractor.json chore: config comments 6 years ago
jest.config.js ci: skip e2e tests on netlify coverage builds 6 years ago
package.json release: v3.0.0-alpha.3 6 years ago
rollup.config.js build: warn invalid format in build script 6 years ago
tsconfig.json chore: Use dynamic paths in tsconfig.json (#548) 6 years ago
yarn.lock build(deps-dev): bump @microsoft/api-extractor from 7.7.5 to 7.7.6 6 years ago

README.md

vue-next CircleCI

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.