theluyuan/vue3-yuanma
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1,447 Commits 1 Branch 0 Tags 21 MiB
TypeScript 97%
HTML 1.4%
JavaScript 1.1%
Vue 0.5%
4659c366e0
Go to file
Evan You 4659c366e0 wip(ssr): generate correct component code
2020-02-06 18:03:14 -05:00
.circleci ci: bust cache 2019-12-20 10:59:21 -05:00
.github chore: update contributing guide [ci skip] 2020-02-05 21:27:03 -05:00
.vscode workflow: support debug single jest test file in vscode (#360) 2019-10-23 11:20:05 -04:00
packages wip(ssr): generate correct component code 2020-02-06 18:03:14 -05:00
scripts build: support source map in build and dev scripts 2020-01-28 10:28:48 -05:00
test-dts test: fix dts tests for 1ccecc0 2020-01-27 16:00:17 -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.4 2020-01-27 16:20:00 -05:00
jest.config.js chore: fix test alias for vue 2020-01-29 18:03:42 -05:00
LICENSE chore: license 2019-10-28 11:15:17 -04:00
package.json workflow: adjust size script 2020-02-06 17:45:46 -05:00
README.md chore: update readme [ci skip] 2020-01-02 18:40:43 -05:00
rollup.config.js build: reduce compiler minified size 2020-02-06 17:45:46 -05:00
tsconfig.json test(ssr): test for rendering components 2020-01-29 16:46:18 -05:00
yarn.lock build(deps-dev): bump puppeteer from 2.1.0 to 2.1.1 2020-02-06 17:16:20 +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.

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.