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

Evan You c28a9196b2 fix(runtime-core): fix globalProperties in check on instance render proxy 6 tahun lalu
.circleci 342d46d82a build: run ls-lint on commit 6 tahun lalu
.github bcb2a9b4a6 build: make @vue/shared public 6 tahun lalu
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) 6 tahun lalu
packages c28a9196b2 fix(runtime-core): fix globalProperties in check on instance render proxy 6 tahun lalu
scripts c017073f4c build: run tests in serial for release 6 tahun lalu
test-dts c1d5928f3b fix(types): accept generic Component type in h() 6 tahun lalu
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 tahun lalu
.ls-lint.yml 412ec86128 fix(types): export missing types from runtime-core (#889) 6 tahun lalu
.prettierrc 3401f6b460 init (graduate from prototype) 7 tahun lalu
CHANGELOG.md c34258fcba chore: fix changelog typo (#918) [ci skip] 6 tahun lalu
LICENSE 34989ef7fe chore: license 6 tahun lalu
README.md 5c33776e67 chore: readme [ci skip] 6 tahun lalu
api-extractor.json d92d310e0f chore: config comments 6 tahun lalu
jest.config.js e93e426bfa feat(runtime-core): config.performance tracing support 6 tahun lalu
package.json 7402951d94 release: v3.0.0-alpha.11 6 tahun lalu
rollup.config.js 4e8d459831 build: tweak flags 6 tahun lalu
tsconfig.json b8c1be18f3 refactor(types): use stricter settings 6 tahun lalu
yarn.lock efa8569b8f build(deps-dev): bump @types/jest from 25.1.5 to 25.2.1 6 tahun lalu

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).

In addition, the current implementation requires native ES2015+ in the runtime environment and does not support IE11 (yet). The IE11 compatible build will be worked on after we have reached RC stage.

Contribution

See Contributing Guide.