a0d570b16d
Static refs still need to be tracked in dynamicChildren because unmount
also takes the fast path when dynamicChildren is present, and all refs
need to be properly unmounted.
This reverts commit
|
||
---|---|---|
.circleci | ||
.github | ||
.vscode | ||
packages | ||
scripts | ||
.gitignore | ||
.prettierrc | ||
api-extractor.json | ||
jest.config.js | ||
lerna.json | ||
package.json | ||
README.md | ||
rollup.config.js | ||
tsconfig.json | ||
yarn.lock |
vue-next
Status: Pre-Alpha.
We have achieved most of the architectural goals and new features planned for v3:
-
Compiler
- Modular architecture
- "Block tree" optimization
- More aggressive static tree hoisting
- Source map support
- Built-in identifier prefixing (aka "stripWith")
- Built-in pretty-printing
- Lean ~10kb brotli-compressed browser build after dropping source map and identifier prefixing
-
Runtime
- Significantly faster
- Simultaneous Composition API + Options API support, with typings
- Proxy-based change detection
- Fragments
- Portals
- Suspense w/
async setup()
However, there are still some 2.x parity features not completed yet:
- Server-side rendering
<keep-alive>
<transition>
v-show
with transition<component :is>
The current implementation also requires native ES2015+ in the runtime environment and does not support IE11 (yet).
Contribution
See Contributing Guide.