add element string to Invariant Exception: Element type is invalid message

[matthargett]

Is this a bug report?

No. This is a missing usability feature that would have saved a fair amount of debugging time.

Have you read the Contributing Guidelines?

Yes.

Environment

React Native on iOS, Android, and Windows.

Environment:
OS: macOS Sierra 10.12.6
Node: 8.9.3
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.2
Android Studio: 3.0.1

Packages: (wanted => installed)
react-native: 0.49.5 => 0.49.5
react: 16.0.0-alpha.5 => 16.0.0-alpha.5

Target Platform: Windows, iOS, Android

Steps to Reproduce

1. import a component from the wrong place (e.g. import ActivityIndicator from 'react-native-windows' instead of import ActivityIndicator from 'react-native'
2. use the incorrectly imported symbol in a JSX tag: render() { return <ActivityIndicator />; }
3. load the app and you get a stack trace similar to Invariant Violation: Element type is invalid: expected a string( for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in. #16332

Actual Behavior

Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined

Expected Behavior

In the actual case, it was a render function with a bunch of tags and it wasn't immediately clear which tag was causing the problem. It would be great if the string of the tag 'ActivityIndicator' could be captured and inserted into the exception message, like this:
Invariant Violation: Element type is invalid for "ActivityIndicator": expected a string (for built-in components) or a class/function (for composite components) but got: undefined

Reproducible Demo

See steps to reproduce.

[react-native-bot]

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

_{How to Contribute • What to Expect from Maintainers}