@vue/compat 3.6.0-rc.14 → 3.6.0-rc.15

package/README.md

@@ -24,11 +24,11 @@ While we've tried hard to make the migration build mimic Vue 2 behavior as much
 
 Please note that the migration build aims to cover only publicly documented Vue 2 APIs and behavior. If your application fails to run under the migration build due to reliance on undocumented behavior, it is unlikely that we'll tweak the migration build to cater to your specific case. Consider refactoring to remove reliance on the behavior in question instead.
 
-A word of caution: if your application is large and complex, migration will likely be a challenge even with the migration build. If your app is unfortunately not suitable for upgrade, do note that we are planning to backport Composition API and some other Vue 3 features to the 2.7 release (estimated late Q3 2021).
+A word of caution: if your application is large and complex, migration will likely be a challenge even with the migration build. If your app is unfortunately not suitable for upgrade, do note that we are planning to backport Composition API and some other Vue 3 features to the 2.7 release.
 
 If you do get your app running on the migration build, you **can** ship it to production before the migration is complete. Although there is a small performance/size overhead, it should not noticeably affect production UX. You may have to do so when you have dependencies that rely on Vue 2 behavior, and cannot be upgraded/replaced.
 
-The migration build will be provided starting with 3.1, and will continue to be published alongside the 3.2 release line. We do plan to eventually stop publishing the migration build in a future minor version (no earlier than EOY 2021), so you should still aim to switch to the standard build before then.
+The migration build will be provided starting with 3.1, and will continue to be published alongside the 3.2 release line. We do plan to eventually stop publishing the migration build in a future minor version, so you should still aim to switch to the standard build before then.
 
 ## Upgrade Workflow
 

package/dist/vue-compat.d.ts

@@ -155,6 +155,8 @@ declare class ReactiveEffect<T = any> implements ReactiveEffectOptions, Reactive
   fn(): T;
   constructor(fn?: () => T);
   get active(): boolean;
+  /** @internal */
+  get running(): boolean;
   pause(): void;
   resume(): void;
   notify(): void;
@@ -342,7 +344,12 @@ declare enum SchedulerJobFlags {
    * Requeue a Suspense effect if its pending branch is discarded.
    * @internal
    */
-  REQUEUE_ON_SUSPENSE_DISCARD = 8
+  REQUEUE_ON_SUSPENSE_DISCARD = 8,
+  /**
+   * A post job buffered by a suspense boundary is queued as soon as that
+   * boundary resolves.
+   */
+  FLUSH_ON_SUSPENSE_RESOLVE = 16
 }
 interface SchedulerJob extends Function {
   order?: number;
@@ -623,6 +630,7 @@ interface SuspenseBoundary {
   deps: number;
   pendingId: number;
   timeout: number;
+  timeoutTimer: ReturnType<typeof setTimeout> | undefined;
   isInFallback: boolean;
   isHydrating: boolean;
   isUnmounted: boolean;
@@ -1071,6 +1079,12 @@ interface VaporInVdomInterface {
    */
   hasTransitionChild(vnode: VNode): boolean;
   getTransitionElement(vnode: VNode): RendererElement | undefined;
+  /**
+   * Enters what vapor mounted under `suspense` while it was pending, right
+   * before the boundary reveals its branch: the boundary's own walk stops
+   * at a vapor component.
+   */
+  enterDeferred(suspense: SuspenseBoundary, enters: Function[]): void;
   /**
    * Re-resolves the hooks of the rows a mounted vapor slot renders under a
    * TransitionGroup (`vnode.vs.group`) and hands over their elements.
@@ -1097,6 +1111,7 @@ interface VdomSlotOptions {
   fallback?: (...args: any[]) => any;
   flags?: number;
   adoptAnchor?: Node;
+  insertionParent?: ParentNode;
 }
 /**
  * The vdom in vapor implementation is in runtime-vapor/src/vdomInterop.ts
@@ -1455,10 +1470,6 @@ interface ComponentInternalOptions {
    * indicates vapor component
    */
   __vapor?: boolean;
-  /**
-   * whether this vapor component has multiple root nodes
-   */
-  __multiRoot?: boolean;
   /**
    * indicates keep-alive component
    */