【Vue】Vue源码第五步——响应式原理（nextTick）

我本人的源代码是比较新的，以前的源码中，nextTick是使用microTimerFunc 和 macroTimerFunc 2 个变量控制异步任务队列的，这里只分析我本地的源码执行流程。

src\core\util\next-tick.js

文件定义了一些主要的变量
callbacks：保存回调函数的一个数组
flushCallbacks：拿到callbacks保存的数组，遍历执行
timerFunc：执行异步回调的方式

// The nextTick behavior leverages the microtask queue, which can be accessed
// via either native Promise.then or MutationObserver.
// MutationObserver has wider support, however it is seriously bugged in
// UIWebView in iOS >= 9.3.3 when triggered in touch event handlers. It
// completely stops working after triggering a few times... so, if native
// Promise is available, we will use it:
/* istanbul ignore next, $flow-disable-line */
if (typeof Promise !== 'undefined' && isNative(Promise)) {
  const p = Promise.resolve()
  timerFunc = () => {
    p.then(flushCallbacks)
    // In problematic UIWebViews, Promise.then doesn't completely break, but
    // it can get stuck in a weird state where callbacks are pushed into the
    // microtask queue but the queue isn't being flushed, until the browser
    // needs to do some other work, e.g. handle a timer. Therefore we can
    // "force" the microtask queue to be flushed by adding an empty timer.
    if (isIOS) setTimeout(noop)
  }
  isUsingMicroTask = true
} else if (!isIE && typeof MutationObserver !== 'undefined' && (
  isNative(MutationObserver) ||
  // PhantomJS and iOS 7.x
  MutationObserver.toString() === '[object MutationObserverConstructor]'
)) {
  // Use MutationObserver where native Promise is not available,
  // e.g. PhantomJS, iOS7, Android 4.4
  // (#6466 MutationObserver is unreliable in IE11)
  let counter = 1
  const observer = new MutationObserver(flushCallbacks)
  const textNode = document.createTextNode(String(counter))
  observer.observe(textNode, {
    characterData: true
  })
  timerFunc = () => {
    counter = (counter + 1) % 2
    textNode.data = String(counter)
  }
  isUsingMicroTask = true
} else if (typeof setImmediate !== 'undefined' && isNative(setImmediate)) {
  // Fallback to setImmediate.
  // Technically it leverages the (macro) task queue,
  // but it is still a better choice than setTimeout.
  timerFunc = () => {
    setImmediate(flushCallbacks)
  }
} else {
  // Fallback to setTimeout.
  timerFunc = () => {
    setTimeout(flushCallbacks, 0)
  }
}

通过上面代码可以看出，根据当前环境来定义timerFunc函数的实现方式，首先判断是否支持promise，其次是MutationObserver，最后实在没办法了就只能通过setTimeout和setImmediate来实现了。

分析nextTick函数

export function nextTick (cb?: Function, ctx?: Object) {
  let _resolve
  callbacks.push(() => {
    if (cb) {
      try {
        cb.call(ctx)
      } catch (e) {
        handleError(e, ctx, 'nextTick')
      }
    } else if (_resolve) {
      _resolve(ctx)
    }
  })
  if (!pending) {
    pending = true
    timerFunc()
  }
  // $flow-disable-line
  if (!cb && typeof Promise !== 'undefined') {
    return new Promise(resolve => {
      _resolve = resolve
    })
  }
}

当调用nextTick函数时候，把cb函数push到callbacks数组中，并且修改this指向让其正确指向调用的vue实例。然后根据pending来判断当前更新队列是否空闲来决定是否调用timerFunc方法，在执行timerFunc时候会把pending设置成true，使得下次的nextTick队列进行等待。当我们执行flushCallbacks时候，又会把pending设置成false让队列代码执行，因为在使用promise中我们flushCallbacks是异步执行的，不影响后续队列进程，但是如果是使用setTimeout执行的话后续队列也要等宏任务执行完才会执行。