Search code examples
reactjsbabeljsreactjs-flux

componentDidUpdate prevProps shows new values when using es6 and Babel

See the TodoMVC app here. Code for the same is here

When you add a todo and edit it, the first value logged in the console should be the value before edit, and the second value, value after edit.

However, both the values logged are values after edit. The prevProps does not get passed. This issue is not seen in the original TodoMVC-flux written in js/jsx by Bill Fisher.

I think this is a bug with Babel but I haven't been able to pinpoint.

Solution

  • The reason why this was happening was due to mutating the state object and gets resolved when you take the immutable approach.

    In the TodoMVC-flux written by Bill Fisher he is returning a new object.

    For more details see https://discuss.reactjs.org/t/componentdidupdate-prevprops-has-new-values-instead-of-old-when-using-es6-and-babel/3695