anchor.diff:    @Deprecated('6.0.0')
     Map getDefaultProps() => throw _unsupportedLifecycleError('getDefaultProps');
   
  -  /// ReactJS lifecycle method that is invoked once, both on the client and server, immediately before the initial
  -  /// rendering occurs.
  -  ///
  -  /// If you call [setState] within this method, [render] will see the updated state and will be executed only once
  -  /// despite the [state] value change.
  -  ///
  -  /// See: <https://facebook.github.io/react/docs/react-component.html#unsafe_componentwillmount>
  +  /// ReactJS lifecycle method that is invoked once immediately before the initial rendering occurs.
     ///
     /// > __DEPRECATED - DO NOT USE__
     /// >
  
positive.code:   @Deprecated('6.0.0')
    void componentWillMount() => throw _unsupportedLifecycleError('componentWillMount');
  
    /// ReactJS lifecycle method that is invoked when a `Component` is receiving [newProps].
    ///
    /// This method is not called for the initial [render].
    ///
    /// Use this as an opportunity to react to a prop transition before [render] is called by updating the [state] using
    /// [setState]. The old props can be accessed via [props].
    ///
    /// Calling [setState] within this function will not trigger an additional [render].
    ///
    /// See: <https://facebook.github.io/react/docs/react-component.html#unsafe_componentwillreceiveprops>
    ///
    /// > __DEPRECATED - DO NOT USE__
    /// >
    /// > This will be removed once 6.0.0 releases, switching to [Component2.getDerivedStateFromProps] is the path forward
    /// >
    /// > React 16 has deprecated [componentWillReceiveProps] in favor of [getDerivedStateFromProps]
    /// >
    /// > This will be completely removed when the JS side of it is slated for removal (ReactJS 17 / react.dart 6.0.0)
    @mustCallSuper
    @Deprecated('6.0.0')
    void componentWillReceiveProps(Map newProps) => throw _unsupportedLifecycleError('componentWillReceiveProps');
  
    /// ReactJS lifecycle method that is invoked immediately before rendering when [nextProps] or [nextState] are being
    /// received.
    ///
    /// This method is not called for the initial [render].
    ///
    /// Use this as an opportunity to perform preparation before an update occurs.
    ///
    /// __Note__: Choose either this method or [componentWillUpdateWithContext]. They are both called at the same time so
    /// using both provides no added benefit.
    ///
    /// See: <https://facebook.github.io/react/docs/react-component.html#unsafe_componentwillupdate>
    ///
    /// > __DEPRECATED - DO NOT USE__
    /// >
    /// > Due to the release of getSnapshotBeforeUpdate in ReactJS 16,
    /// > componentWillUpdate is no longer the method used to check the state
    /// > and props before a re-render. Additionally, because of the presence
    /// > of getSnapshotBeforeUpdate, componentWillUpdate will be ignored. Use
    /// > getSnapshotBeforeUpdate instead.
    /// >
    /// > This will be completely removed when the JS side of it is slated for removal (ReactJS 17 / react.dart 6.0.0)
    @mustCallSuper
    @Deprecated('6.0.0')
    void componentWillUpdate(Map nextProps, Map nextState) => throw _unsupportedLifecycleError('componentWillUpdate');
  
negative.code:   /// Use this as an opportunity to operate on the [rootNode] (DOM) when the `Component` has been updated as a result
    /// of the values of [prevProps] / [prevState].
    ///
    /// __Note__: React 16 added a third parameter to `componentDidUpdate`, which
    /// is a custom value returned from [getSnapshotBeforeUpdate]. If a
    /// value is not returned from [getSnapshotBeforeUpdate], the [snapshot]
    /// parameter in `componentDidUpdate` will be null.
    ///
    /// See: <https://reactjs.org/docs/react-component.html#componentdidupdate>
    void componentDidUpdate(Map prevProps, Map prevState, [dynamic snapshot]) {}
  
    /// ReactJS lifecycle method that is invoked immediately before a `Component` is unmounted from the DOM.
  