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

Evan You 77103e1fd7 types: fix tsx dts tests преди 6 години
.circleci 2dcdbca6e2 ci: bust cache преди 6 години
.github e6b0006b40 chore: add GitHub sponsor button config (#708) [ci skip] преди 6 години
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) преди 6 години
packages 77103e1fd7 types: fix tsx dts tests преди 6 години
scripts 78beed2574 build: support source map in build and dev scripts преди 6 години
test-dts 77103e1fd7 types: fix tsx dts tests преди 6 години
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) преди 6 години
.prettierrc 3401f6b460 init (graduate from prototype) преди 7 години
CHANGELOG.md d293876c34 release: v3.0.0-alpha.4 преди 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 32d6a46474 build: avoid runtime wildcard import in global build преди 6 години
package.json 77103e1fd7 types: fix tsx dts tests преди 6 години
rollup.config.js 77103e1fd7 types: fix tsx dts tests преди 6 години
tsconfig.json 8cdaf28515 test(ssr): test for rendering components преди 6 години
yarn.lock 0fc720c34a build(deps): bump csstype from 2.6.8 to 2.6.9 (#722) преди 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.