🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

dependabot-preview[bot] f924bd68bc build(deps-dev): bump rollup from 2.3.0 to 2.3.1 (#900) 6 anni fa
.circleci 342d46d82a build: run ls-lint on commit 6 anni fa
.github bcb2a9b4a6 build: make @vue/shared public 6 anni fa
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) 6 anni fa
packages 37b1dc8242 fix(transition): warn only when there is more than one rendered child (#903) 6 anni fa
scripts 4e8d459831 build: tweak flags 6 anni fa
test-dts e67f655b26 refactor(runtime-core): revert setup() result reactive conversion 6 anni fa
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 anni fa
.ls-lint.yml 412ec86128 fix(types): export missing types from runtime-core (#889) 6 anni fa
.prettierrc 3401f6b460 init (graduate from prototype) 7 anni fa
CHANGELOG.md de81faf00a release: v3.0.0-alpha.10 6 anni fa
LICENSE 34989ef7fe chore: license 6 anni fa
README.md 394fd4c6aa chore: readme [ci skip] 6 anni fa
api-extractor.json d92d310e0f chore: config comments 6 anni fa
jest.config.js 32d6a46474 build: avoid runtime wildcard import in global build 6 anni fa
package.json d777ac6549 build(deps): bump rollup 6 anni fa
rollup.config.js 4e8d459831 build: tweak flags 6 anni fa
tsconfig.json b8c1be18f3 refactor(types): use stricter settings 6 anni fa
yarn.lock f924bd68bc build(deps-dev): bump rollup from 2.3.0 to 2.3.1 (#900) 6 anni fa

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.