Go to file

Evan You ca5f39ee35 refactor(runtime-core): adjust patchProp value arguments order

BREAKING CHANGE: `RendererOptions.patchProp` arguments order has changed

  The `prevValue` and `nextValue` position has been swapped to keep it
  consistent with other functions in the renderer implementation. This
  only affects custom renderers using the `createRenderer` API.

2020-03-09 16:15:49 -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

refactor(runtime-core): adjust patchProp value arguments order

2020-03-09 16:15:49 -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.8

2020-03-06 15:58:40 -05: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.8

2020-03-06 15:58:40 -05:00

README.md

chore: readme

2020-02-18 14:56:53 -05:00

rollup.config.js

build: make @vue/shared public

2020-02-29 22:04:42 -05:00

tsconfig.json

test(ssr): test for rendering components

2020-01-29 16:46:18 -05:00

yarn.lock

build(deps-dev): bump rollup from 1.32.0 to 1.32.1 (#810 )

2020-03-09 15:57:28 -04:00

README.md

vue-next

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.