It still makes sense in case you want to have abstraction on top of your state. You won’t have any performance wins using reselect in this case, so you can just do smth like
const getUserName = (state) => state.auth.userName . It definitely will reduce your refactoring effort, in case you want to change the shape of your state.
AWS recently announced Lambda Layers https://aws.amazon.com/about-aws/whats-new/2018/11/aws-lambda-now-supports-custom-runtimes-and-layers/ so it should be even easier to use native modules
There is a golden rule, use PureComponent only when you may experience performance regression. In some cases it can be even faster to let react do it’s job.
This is quite interesting. Would be great to hear clarification from Google regarding this statement. Is there any failure cases related to auto insertion?
We ended up all code style debates since started using eslint + prettier.