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

Evan You cc69fd72e3 fix(reactivity): Map/Set identity methods should work even if raw value contains reactive entries 6 rokov pred
.circleci 2dcdbca6e2 ci: bust cache 6 rokov pred
.github bcb2a9b4a6 build: make @vue/shared public 6 rokov pred
.vscode 11d0778f9c workflow: support debug single jest test file in vscode (#360) 6 rokov pred
packages cc69fd72e3 fix(reactivity): Map/Set identity methods should work even if raw value contains reactive entries 6 rokov pred
scripts c3028ad6b3 build: remove compiler-ssr and server-renderer from skipped packages 6 rokov pred
test-dts e67f655b26 refactor(runtime-core): revert setup() result reactive conversion 6 rokov pred
.gitignore 0478ca4cdb chore: add the yarn error log file to git ignore (#150) 6 rokov pred
.prettierrc 3401f6b460 init (graduate from prototype) 7 rokov pred
CHANGELOG.md 312513d255 release: v3.0.0-alpha.7 6 rokov pred
LICENSE 34989ef7fe chore: license 6 rokov pred
README.md 8f463b3859 chore: readme 6 rokov pred
api-extractor.json d92d310e0f chore: config comments 6 rokov pred
jest.config.js 32d6a46474 build: avoid runtime wildcard import in global build 6 rokov pred
package.json bcb2a9b4a6 build: make @vue/shared public 6 rokov pred
rollup.config.js bcb2a9b4a6 build: make @vue/shared public 6 rokov pred
tsconfig.json 8cdaf28515 test(ssr): test for rendering components 6 rokov pred
yarn.lock e6ef52c3f8 build(deps-dev): bump typescript from 3.8.2 to 3.8.3 6 rokov pred

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.

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).

TODOs as of 3.0.0-alpha.5

  • Suspense support in SSR
  • SSR Hydration mismatch handling
  • SSR vnode directive support
  • SSR integration tests
  • 2.x compatible async component support

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.