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

Claudio Eyzaguirre a35e2970b2 chore: fix typo in Chagelog.md (#960) [ci skip] пре 6 година
.circleci 342d46d82a build: run ls-lint on commit пре 6 година
.github bcb2a9b4a6 build: make @vue/shared public пре 6 година
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) пре 6 година
packages 7cbf684611 fix(runtime-core): fix kebab-case props update пре 6 година
scripts 2c9374dd91 build: remove size check for runtime.global files пре 6 година
test-dts 33ccfc0a8b fix(types): UnwrapRef should bail on DOM element types (#952) пре 6 година
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) пре 6 година
.ls-lint.yml 412ec86128 fix(types): export missing types from runtime-core (#889) пре 6 година
.prettierrc 3401f6b460 init (graduate from prototype) пре 7 година
CHANGELOG.md a35e2970b2 chore: fix typo in Chagelog.md (#960) [ci skip] пре 6 година
LICENSE 34989ef7fe chore: license пре 6 година
README.md 5c33776e67 chore: readme [ci skip] пре 6 година
api-extractor.json d92d310e0f chore: config comments пре 6 година
jest.config.js e93e426bfa feat(runtime-core): config.performance tracing support пре 6 година
package.json 1d9f8fc979 release: v3.0.0-alpha.12 пре 6 година
rollup.config.js 4e8d459831 build: tweak flags пре 6 година
tsconfig.json b8c1be18f3 refactor(types): use stricter settings пре 6 година
yarn.lock 29718e4836 build(deps-dev): bump @rollup/plugin-node-resolve from 7.1.1 to 7.1.3 пре 6 година

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.