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

dependabot-preview[bot] e683cc6ed4 build(deps-dev): bump enquirer from 2.3.2 to 2.3.4 6 лет назад
.circleci 2dcdbca6e2 ci: bust cache 6 лет назад
.github 7c90aa5539 chore: fix typo in contributing guide (#589) 6 лет назад
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) 6 лет назад
packages 9f65d811af release: v3.0.0-alpha.2 6 лет назад
scripts 1d5a9eb7c1 chore: fix publish log [ci skip] 6 лет назад
test-dts 74baea108a fix(types): components options should accept components defined with defineComponent (#602) 6 лет назад
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 лет назад
.prettierrc 3401f6b460 init (graduate from prototype) 7 лет назад
CHANGELOG.md 9f65d811af release: v3.0.0-alpha.2 6 лет назад
LICENSE 34989ef7fe chore: license 6 лет назад
README.md 7770d6d034 chore: update readme [ci skip] 6 лет назад
api-extractor.json d92d310e0f chore: config comments 6 лет назад
jest.config.js 80f8b46177 ci: skip e2e tests on netlify coverage builds 6 лет назад
package.json 9f65d811af release: v3.0.0-alpha.2 6 лет назад
rollup.config.js c3e1c812e3 build: warn invalid format in build script 6 лет назад
tsconfig.json c57837c324 chore: Use dynamic paths in tsconfig.json (#548) 6 лет назад
yarn.lock e683cc6ed4 build(deps-dev): bump enquirer from 2.3.2 to 2.3.4 6 лет назад

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.