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

Evan You bc07e95ca8 fix(ssr): avoid hard-coded ssr checks in cjs builds 6 years ago
.circleci 2dcdbca6e2 ci: bust cache 6 years ago
.github 78beed2574 build: support source map in build and dev scripts 6 years ago
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) 6 years ago
packages bc07e95ca8 fix(ssr): avoid hard-coded ssr checks in cjs builds 6 years ago
scripts 78beed2574 build: support source map in build and dev scripts 6 years ago
test-dts 8c892e0392 test: fix dts tests for 1ccecc0 6 years ago
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 years ago
.prettierrc 3401f6b460 init (graduate from prototype) 7 years ago
CHANGELOG.md d293876c34 release: v3.0.0-alpha.4 6 years ago
LICENSE 34989ef7fe chore: license 6 years ago
README.md 7770d6d034 chore: update readme [ci skip] 6 years ago
api-extractor.json d92d310e0f chore: config comments 6 years ago
jest.config.js bc07e95ca8 fix(ssr): avoid hard-coded ssr checks in cjs builds 6 years ago
package.json d293876c34 release: v3.0.0-alpha.4 6 years ago
rollup.config.js bc07e95ca8 fix(ssr): avoid hard-coded ssr checks in cjs builds 6 years ago
tsconfig.json c57837c324 chore: Use dynamic paths in tsconfig.json (#548) 6 years ago
yarn.lock 827fd05644 build(deps-dev): bump @microsoft/api-extractor from 7.7.7 to 7.7.8 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.