I feel like detecting interopRequireWildcard specifically is fragile, but:

1. I can't think of a better pattern
2. Most modules on npm aren't minified anyway

@nicolo-ribaudo how reliable is the _interopRequireWildcard name here (with the _)? I know it's fragile, it would just be nice to get a sense of how fragile. Should we support without the leading _, and possibly with $n?

Babel will never inject it without the leading _.

$n could happen when you compile a file which has already been compiled (thus it already contains an _interopRequireWildcard function). When people compile re-compile files it's almost always because they are bundling and compiling their dependencies: in this case Babel's exports wouldn't be the final bundle exports anyway. I don't think we need to worry about it.

Thanks for confirming!