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

likui 63a6563106 fix(reactivity): should delete observe value (#598) 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 63a6563106 fix(reactivity): should delete observe value (#598) 6 سال پیش
scripts 4154cacc76 chore(scripts): fix typo (#612) 6 سال پیش
test-dts 7df5e70c83 types: accept defineComponent return types in app.mount 6 سال پیش
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 سال پیش
.prettierrc 3401f6b460 init (graduate from prototype) 7 سال پیش
CHANGELOG.md 1bb1271b5e release: v3.0.0-alpha.1 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 54bb820f73 types: update jsx support (#587) 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 30aae0b4df build(deps): bump postcss from 7.0.25 to 7.0.26 (#570) 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.