Confusing error when passing non-function to useMemo

[aweary]

Example.

When passing something like an object to useMemo the error isn't very helpful.

TypeError: nextCreate is not a function
    at mountMemo (https://grhhp.csb.app/node_modules/react-dom/cjs/react-dom.development.js:13459:19)
    ...

Most developers wont know what nextCreate is, and passing an object to useMemo doesn't seem obviously wrong at first. We could add a typeof check that throws a better error, but maybe that's too much overhead? At the very least we could add a DEV warning with more helpful guidance.

[threepointone]

Huh. This is usually caught by flow/typescript, but I can see why it might be confusing without a type system. Do you believe this is a common problem? If so, maybe a DEV warning would be good.

[Tevinthuku]

@threepointone , If you resolve to have a dev warning for this, I could work on that

[duanebester]

@aweary I have an incoming PR for this

[caspercasanova]

Why is this still open?

[jeanpierrecarvalho]

Why is this still open?

@duanebester

[duanebester]

Add DEV warning for when a non-function is passed to useMemo #17529

No one ever approved my PR, so I closed it