Connect throws an error when connecting a memoized component

[Maushundb]

After upgrading my project to React 16.6.0 and migrating components to React.memo instead of Recompose.pure, connect is throwing an error when passed a memoized component:

Uncaught Error: You must pass a component to the function returned by connect. Instead received {"compare":null}

Repro:

const mapStateToProps = () => ({});
const MyComponent = React.memo(() => <div />);
const MyConnectedComponent = connect(mapStateToProps)(MyComponent);
ReactDOM.render(
  <MyConnectedComponent />,
  document.getElementById('root'),
);

[markerikson]

Duplicate of #914 . This will be fixed in React-Redux 6.0. Please try out our current WIP branches at #995 and #1000 to see if they work okay, available on NPM as tags next-995 and next-1000. I'll close this, but go ahead and comment here to let us know if they fix the issue for you.

(It's actually entirely possible they might not work right here - we might need to rebuild against React 16.6+ / a current version of react-is, in case we need to pick up the code that indicates that "memo" is a valid component type.)

[Maushundb]

The next-1000 tag does NOT seem to fix my issue, unfortunately. Thanks for the timely response regardless!

[markerikson]

Okay, thanks for the info.

I'm reconsidering this a bit - it may be worth putting out a 5.0.8 / 5.1.0 build that only switches to use of react-is, as an interim change.

[ddzy]

After upgrading my project to React 16.6.0 and migrating components to React.memo instead of Recompose.pure, connect is throwing an error when passed a memoized component:

Uncaught Error: You must pass a component to the function returned by connect. Instead received {"compare":null}

Repro:

const mapStateToProps = () => ({});
const MyComponent = React.memo(() => <div />);
const MyConnectedComponent = connect(mapStateToProps)(MyComponent);
ReactDOM.render(
  <MyConnectedComponent />,
  document.getElementById('root'),
);

same issue

[markerikson]

@ddzy : please provide a project that reproduces the issue, preferably in CodeSandbox.