theluyuan/vue3-yuanma
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1,664 Commits 1 Branch 0 Tags 21 MiB
TypeScript 97%
HTML 1.4%
JavaScript 1.1%
Vue 0.5%
ebc1ca8eff
Go to file
Evan You ebc1ca8eff fix(suspense): clear effects on suspense resolve
2020-03-18 15:40:20 -04:00
.circleci ci: bust cache 2019-12-20 10:59:21 -05:00
.github build: make @vue/shared public 2020-02-29 22:04:42 -05:00
.vscode workflow: support debug single jest test file in vscode (#360) 2019-10-23 11:20:05 -04:00
packages fix(suspense): clear effects on suspense resolve 2020-03-18 15:40:20 -04:00
scripts build: remove compiler-ssr and server-renderer from skipped packages 2020-02-18 14:56:53 -05:00
test-dts refactor(runtime-core): revert setup() result reactive conversion 2020-02-26 19:01:42 -05:00
.gitignore chore: add the yarn error log file to git ignore (#150) 2019-10-09 12:13:54 -04:00
.prettierrc init (graduate from prototype) 2018-09-19 11:35:38 -04:00
api-extractor.json chore: config comments 2019-09-03 12:17:33 -04:00
CHANGELOG.md release: v3.0.0-alpha.9 2020-03-16 18:56:44 -04:00
jest.config.js build: avoid runtime wildcard import in global build 2020-02-13 18:50:36 -05:00
LICENSE chore: license 2019-10-28 11:15:17 -04:00
package.json release: v3.0.0-alpha.9 2020-03-16 18:56:44 -04:00
README.md chore: update readme todo [ci skip] 2020-03-16 18:59:10 -04:00
rollup.config.js feat(ssr/suspense): suspense hydration 2020-03-13 13:05:05 -04:00
tsconfig.json test(ssr): test for rendering components 2020-01-29 16:46:18 -05:00
yarn.lock build(deps-dev): bump @microsoft/api-extractor from 7.7.8 to 7.7.9 2020-03-18 07:50:09 +00:00

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

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