_interopRequireWildcard breaks on nodejs cases

[theKashey]

Bug Report

The bug was introduced by #10161, v7.5.5 is confirmed to work

Current Behavior

• Given a code import * as isNode from 'detect-node'; (TypeScript syntax)
• Compiles to es5 code const isNode = require('detect-node') (again TypeScript)
• Parcel bundler then compiles es2015 code to the following

const isNode = _interopRequireWildcard(require('detect-node'));

The result would be correct, however, internally it uses WeakMap based cache, and by some reason, expects any module to be resolved to an object.

https://github.com/babel/babel/blob/master/packages/babel-helpers/src/helpers.js#L623-L626

var cache = _getRequireWildcardCache();
    if (cache && cache.has(obj)) {
      return cache.get(obj);
    }

require('detect-node') resolves to true or false

A clear and concise description of the behavior.

Input Code

_interopRequireWildcard(false); // throws

Expected behavior/code

_interopRequireWildcard(false) === false
_interopRequireWildcard(42) === 42
_interopRequireWildcard(function) === function (!!)

import * as cx from 'classnames'; is also not working, even at 7.5.5

Possible Solution
Many "object like" structures are not "WeakMapable", however - typeof value === 'object' would be more than enought.

[babel-bot]

Hey @theKashey! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."

[jridgewell]

Closing as a dupe of #10561, PR at #10574.

[jridgewell]

Sorry for being brief. This was an excellent bug report, and thank you for filling it!

[theKashey]

No worries.
But I've added a comment to PR for the case module.exports = function