pure component

1// history.js
2import { createBrowserHistory } from 'history'
3
4export default createBrowserHistory({
5  /* pass a configuration object here if needed */
6})

1import { browserHistory } from 'react-router';
2browserHistory.push('/some/path');

1The major difference between React.PureComponent and React.Component is PureComponent does a shallow comparison on state change. It means that when comparing scalar values it compares their values, but when comparing objects it compares only references. It helps to improve the performance of the app.
2
3You should go for React.PureComponent when you can satisfy any of the below conditions.
4
5    State/Props should be an immutable object
6    State/Props should not have a hierarchy
7    You should call forceUpdate when data changes
8
9If you are using React.PureComponent you should make sure all child components are also pure.
10
11    is there any performance impact in using React.component that we may consider going for React.PureComponent?
12
13Yes, it will increase your app performance (because of shallow comparison)
14
15    I am guessing shouldComponentUpdate() of Purecomponent performs only shallow comparisons . If this is the case can' t the said method used for deeper comparisons?
16
17You guessed it correctly. You could use it if you satisfy any of the conditions I mentioned above.
18
19    "Furthermore, React.PureComponent's shouldComponentUpdate() skips prop updates for the whole component subtree" - Does this mean that prop changes are ignored?
20
21Yes, prop changes will be ignored If it couldn't find difference in shallow comparison.