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

Evan You 797cc18967 wip(ssr): element scopeId 6 vuotta sitten
.circleci 2dcdbca6e2 ci: bust cache 6 vuotta sitten
.github 27e2e482e9 chore: update contributing guide [ci skip] 6 vuotta sitten
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) 6 vuotta sitten
packages 797cc18967 wip(ssr): element scopeId 6 vuotta sitten
scripts 78beed2574 build: support source map in build and dev scripts 6 vuotta sitten
test-dts 8c892e0392 test: fix dts tests for 1ccecc0 6 vuotta sitten
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 vuotta sitten
.prettierrc 3401f6b460 init (graduate from prototype) 7 vuotta sitten
CHANGELOG.md d293876c34 release: v3.0.0-alpha.4 6 vuotta sitten
LICENSE 34989ef7fe chore: license 6 vuotta sitten
README.md 7770d6d034 chore: update readme [ci skip] 6 vuotta sitten
api-extractor.json d92d310e0f chore: config comments 6 vuotta sitten
jest.config.js 9cf4518936 chore: fix test alias for vue 6 vuotta sitten
package.json 605cc3db17 workflow: adjust size script 6 vuotta sitten
rollup.config.js 9cfbab0686 build: reduce compiler minified size 6 vuotta sitten
tsconfig.json 8cdaf28515 test(ssr): test for rendering components 6 vuotta sitten
yarn.lock 85a2a41780 build(deps-dev): bump puppeteer from 2.1.0 to 2.1.1 6 vuotta sitten

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.