v6: prefer components in normalizeComponent

[henryqdineen]

We have been using v6.10.0 and one of our cell components was changed to use React.memo and the table unexpectedly stopped working. It looks like other have users reported issues with normalizeComponent in various versions and some fixes have been made.

Unfortunately some users have code that assumes the "components" are just a element factory and not a true React component. When these React components are defined inline this can cause unmounts when the parent component is re-rendered. This branch will not fix that issue but I think instead users should avoid creating inline components and just use React context if you absolutely need to provide anything to these components.

The fix for us was to use isValidElementType from react-is for component detection and allow us to use React.memo, React.forwardRef, etc. We think this solution is cleaner and providers a more predictable API. We weren't comfortable with the existing String(component).includes('.createElement') detection and have a lot of examples where that fails.

I understand that this probably won't be merged but it could be helpful for others that might fork this lib. Thanks!

Other changes

• updated prop-types peer dep to ^15.7.0 because that is when elementType was introduced
• add react-is peer dep
• update column "renderer" prop types to more closely reflect the new logic in normalizeComponent

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit ec3fb68:

Sandbox	Source
zealous-gauss-409tz	Configuration

[leeyeh]

Just running into the same issue with React.memo and React.forwardRefwrapped component.

Hope this PR got landed soon.

[tannerlinsley]

Make react-is a direct dependency and you've got yourself a deal.

[henryqdineen]

Done! Thanks