feat(ssr/suspense): suspense hydration

In order to support hydration of async components, server-rendered
fragments must be explicitly marked with comment nodes.

build(deps-dev): bump minimist from 1.2.4 to 1.2.5

Bumps [minimist](https://github.com/substack/minimist) from 1.2.4 to 1.2.5.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.4...1.2.5)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

feat(runtime-core): implement RFC-0020

BREAKING CHANGE: data no longer supports object format (per RFC-0020)

feat(runtime-core): add special property to get class component options (#821)

fix(types): app.component should accept defineComponent return type (#822)

fix #730

build(deps-dev): bump minimist from 1.2.3 to 1.2.4

Bumps [minimist](https://github.com/substack/minimist) from 1.2.3 to 1.2.4.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.3...1.2.4)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

fix(runtime-core): always set invalid vnode type (#820)

Currently, when a component used is not properly registered, we have a warning and the vnode type is set to a Comment type in DEV mode. But in prod mode, we have no default value, making such an application broken and throw a strange error (`can not read _isSuspense of undefined`).

This commit avoids such an error in prod mode (as it is currently the case in Vue 2.x).

fix(build): remove __RUNTIME_COMPILE__ flag

behavior should be consistent in all builds. fix #817

refactor(Suspense): remove unnecessary casts (#819)

build(deps-dev): bump minimist from 1.2.0 to 1.2.3

Bumps [minimist](https://github.com/substack/minimist) from 1.2.0 to 1.2.3.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.0...1.2.3)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

test: fix & improve ssr warning assertion

feat(ssr): compiler-ssr support for Suspense

refactor(ssr): improve ssr async setup / suspense error handling

test(srr): group portal tests

build(deps-dev): bump rollup-plugin-terser from 5.2.0 to 5.3.0

Bumps [rollup-plugin-terser](https://github.com/TrySound/rollup-plugin-terser) from 5.2.0 to 5.3.0.
- [Release notes](https://github.com/TrySound/rollup-plugin-terser/releases)
- [Commits](https://github.com/TrySound/rollup-plugin-terser/compare/v5.2.0...v5.3.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

feat(server-renderer): render suspense in vnode mode (#727)

test(runtime-core/renderer): tests for rendering elements (#699)

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.

fix(runtime-core): pass prev value to hostPatchProp (#809)

fix #808

fix(runtime-core): should allow empty string and 0 as valid vnode key (#807)

types(reactivity): remove this in get accessor, fix #800 (#806)

types(runtime-core): update error type to unknown (#798)

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

Bumps [rollup](https://github.com/rollup/rollup) from 1.32.0 to 1.32.1.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rollup/rollup/compare/v1.32.0...v1.32.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>

release: v3.0.0-alpha.8

test(ssr): test for hydration mismatch handling

test(ssr): ssr + hydration integration test

fix(ssr): fix ssr on-the-fly compilation + slot fallback branch helper injection

fix(reactivity): allow effect trigger inside no-track execution contexts

fix #804

chore(template-explorer): bump monaco version for live deployed page

chore(template-explorer): update monaco dependency (#793)

types(reactivity): add undefined type to ref/shallowRef when no args (#791)

fix(reactivity): should not trigger length dependency on Array delete

close #774

build(deps): bump @babel/parser from 7.8.6 to 7.8.7 (#797)

Bumps [@babel/parser](https://github.com/babel/babel) from 7.8.6 to 7.8.7.
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/compare/v7.8.6...v7.8.7)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>

build(deps): bump @babel/types from 7.8.6 to 7.8.7 (#796)

Bumps [@babel/types](https://github.com/babel/babel) from 7.8.6 to 7.8.7.
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/compare/v7.8.6...v7.8.7)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>

fix(reactivity): Map/Set identity methods should work even if raw value contains reactive entries

fix #799

types: remove 'this' annotation from 'get' accessor (#801)

The next version of Typescript disallows 'this' parameter annotations on
accessors, which causes vue-next to fail to compile.

This PR removes the annotation and adds a cast instead.

Fixes #800

test(ssr): more hydration tests

test(ssr): hydratioon tests (wip)

feat(ssr): hydration mismatch handling

fix(directives): ignore invalid directive hooks

fix #795

chore: fix componentRenderUtils.ts comment typo (#790) [ci skip]

build(deps-dev): bump typescript from 3.8.2 to 3.8.3

Bumps [typescript](https://github.com/Microsoft/TypeScript) from 3.8.2 to 3.8.3.
- [Release notes](https://github.com/Microsoft/TypeScript/releases)
- [Commits](https://github.com/Microsoft/TypeScript/compare/v3.8.2...v3.8.3)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

chore: update @vue/shared readme [ci skip]

build: make @vue/shared public

This avoids it being inlined multiple times in esm bundler builds

refactor(runtime-core): adjust attr fallthrough behavior

BREAKING CHANGE: adjust attr fallthrough behavior

    Updated per pending RFC https://github.com/vuejs/rfcs/pull/137

    - Implicit fallthrough now by default only applies for a whitelist
      of attributes (class, style, event listeners, a11y attributes, and
      data attributes).

    - Fallthrough is now applied regardless of whether the component has
      explicitly declared props. (close #749)

build(deps-dev): bump rollup from 1.31.1 to 1.32.0

Bumps [rollup](https://github.com/rollup/rollup) from 1.31.1 to 1.32.0.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rollup/rollup/compare/v1.31.1...v1.32.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

fix(runtime-core): ensure inhertied attrs update on optimized child root

fix #677, close #784

chore: fix snapshot

feat(compiler-core): switch to @babel/parser for expression parsing

    This enables default support for parsing bigInt, optional chaining
    and nullish coalescing, and also adds the `expressionPlugins`
    compiler option for enabling additional parsing plugins listed at
    https://babeljs.io/docs/en/next/babel-parser#plugins.

refactor(hydration): move fragment to seaprate function + skip normalization in optimized mode

fix(slots): fix conditional slot

fix #787

test: fix options usage of reactive

refactor(runtime-core): revert setup() result reactive conversion

BREAKING CHANGE: revert setup() result reactive conversion

    Revert 6b10f0c & a840e7d. The motivation of the original change was
    avoiding unnecessary deep conversions, but that can be achieved by
    explicitly marking values non-reactive via `markNonReactive`.

    Removing the reactive conversion behavior leads to an usability
    issue in that plain objects containing refs (which is what most
    composition functions will return), when exposed as a nested
    property from `setup()`, will not unwrap the refs in templates. This
    goes against the "no .value in template" intuition and the only
    workaround requires users to manually wrap it again with `reactive()`.

    So in this commit we are reverting to the previous behavior where
    objects returned from `setup()` are implicitly wrapped with
    `reactive()` for deep ref unwrapping.

refactor(fragments): remove visible anchors for fragments

fix(portal): fix portal placeholder text

refactor(compiler-ssr): extract portal processing + emit errors

feat(compiler-ssr): compile portal (#775)

release: v3.0.0-alpha.7

refactor: use consistent name for watch invalidation register function

fix(runtime-core): set appContext.provides to Object.create(null) (#781)

fix(template-explorer): rename watch -> watchEffect (#780)

chore: fixes a small typo and prettifies the document (#778)

build(deps-dev): bump @types/puppeteer from 2.0.0 to 2.0.1

Bumps [@types/puppeteer](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/puppeteer) from 2.0.0 to 2.0.1.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/puppeteer)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

fix(types): shallowRef should not unwrap value type

test: add type test for nested refs in ref.value

fix(types): ref value type unwrapping should happen at creation time

refactor: remove old watch signature support

refactor(directives): remove binding.instance

BREAKING CHANGE: custom directive bindings no longer expose instance

    This is a rarely used property that creates extra complexity in
    ensuring it points to the correct instance. From a design
    perspective, a custom directive should be scoped to the element and
    data it is bound to and should not have access to the entire
    instance in the first place.

fix(template-ref): fix string template refs inside slots

fix(renderSlot): set slot render as a STABLE_FRAGMENT (#776)

fix #766

fix(runtime-core): fix slot fallback + slots typing

fix #773

fix(runtime-core): make watchEffect ignore deep option (#765)

chore: fix typo (#764) [ci skip]

refactor(ssr): extract buffer resolving and resolvePortals (#771)

chore: changelog edits [ci skip]

release: v3.0.0-alpha.6

feat(runtime-core): add watchEffect API

BREAKING CHANGE: replae `watch(fn, options?)` with `watchEffect`

    The `watch(fn, options?)` signature has been replaced by the new
    `watchEffect` API, which has the same usage and behavior. `watch`
    now only supports the `watch(source, cb, options?)` signautre.

chore: remove debugger [ci skip]

perf(effect): optimize effect trigger for array length mutation (#761)

feat(reactivity): expose unref and shallowRef

chore: fix test type

refactor: preserve refs in reactive arrays

BREAKING CHANGE: reactive arrays no longer unwraps contained refs

    When reactive arrays contain refs, especially a mix of refs and
    plain values, Array prototype methods will fail to function
    properly - e.g. sort() or reverse() will overwrite the ref's value
    instead of moving it (see #737).

    Ensuring correct behavior for all possible Array methods while
    retaining the ref unwrapping behavior is exceedinly complicated; In
    addition, even if Vue handles the built-in methods internally, it
    would still break when the user attempts to use a 3rd party utility
    functioon (e.g. lodash) on a reactive array containing refs.

    After this commit, similar to other collection types like Map and
    Set, Arrays will no longer automatically unwrap contained refs.

    The usage of mixed refs and plain values in Arrays should be rare in
    practice. In cases where this is necessary, the user can create a
    computed property that performs the unwrapping.

fix(types): improve ref typing, close #759

perf(reactivity): only trigger all effects on Array length mutation if new length is shorter than old length

build(deps-dev): bump typescript from 3.7.5 to 3.8.2

Bumps [typescript](https://github.com/Microsoft/TypeScript) from 3.7.5 to 3.8.2.
- [Release notes](https://github.com/Microsoft/TypeScript/releases)
- [Commits](https://github.com/Microsoft/TypeScript/commits)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

chore: typo (#744) [ci skip]

test(reactivity): test for ref without init value (#746)

fix(sfc): inherit parent scopeId on child rooot (#756)

fix(compiler-dom): properly stringify class/style bindings when hoisting static strings

chore: use undefined for TS 3.8 compat

fix(reactivity): should trigger all effects when array length is mutated (#754)

chore: use 'const' instead of 'let' (#755) [ci skip]

fix(types): update setup binding unwrap types for 6b10f0c

close #738

build: use buildOption to determine runtime compile build (#742)

This makes it possible to create a separate package that uses runtime compilation.

fix(compiler-core): should alias name in helperString (#743)

fix #740

release: v3.0.0-alpha.5

chore: readme

build: remove compiler-ssr and server-renderer from skipped packages

build(deps): bump postcss from 7.0.26 to 7.0.27 (#734)

Bumps [postcss](https://github.com/postcss/postcss) from 7.0.26 to 7.0.27.
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/master/CHANGELOG.md)
- [Commits](https://github.com/postcss/postcss/compare/7.0.26...7.0.27)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

fix(runtime-core): ensure renderCache always exists