Just about every time I set up a new `Context.Provider`, I end up accidentally specifying a `values` prop rather than `value`.  While it's a minor error, generally I build the container in which the provider resides and commit it to the code base before I ever use it.  It's only later when I go to use it that I realize I did it again.  Since the `Context.Provider` seems pretty much useless without a `value` prop specified, I'd love it if there was a prop error if it is missing... especially if another prop is defined on the `Context.Provider` instead.
workInProgress.lanes = NoLanes;
          return updateOffscreenComponent(current, workInProgress, renderLanes);
        }
      }
      return bailoutOnAlreadyFinishedWork(current, workInProgress, renderLanes);
    } else {
      
      
      
      
      didReceiveUpdate = false;
    }
  } else {
    didReceiveUpdate = false;
  }
   Before entering the begin phase, clear pending update priority.
   TODO: This assumes that we're about to evaluate the component and process
   the update queue. However, there's an exception: SimpleMemoComponent
   sometimes bails out later in the begin phase. This indicates that we should
   move this assignment out of the common path and into each branch.
  workInProgress.lanes = NoLanes;
  switch (workInProgress.tag) {