You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So we can only usemod = require('xx') but not mod = require('xx').default any more if we don't set "addDefaultProperty" to true.
However, both function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { "default": obj }; } in Babel and
in webpack imports a module harmonly depending on whethermodule.__esModule is true which may import undefined from module.default.
So will it better set "__esModule" to false when "addDefaultProperty" is false in order to tell Babel and webpack import module from module.exports instead of module.exports.default?
The text was updated successfully, but these errors were encountered:
The plugin helps us set
So we can only use
mod = require('xx')
but notmod = require('xx').default
any more if we don't set "addDefaultProperty" to true.However, both
function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { "default": obj }; }
in Babel andin webpack imports a module harmonly depending on whether
module.__esModule
is true which may importundefined
frommodule.default
.So will it better set "__esModule" to false when "addDefaultProperty" is false in order to tell Babel and webpack import module from
module.exports
instead ofmodule.exports.default
?The text was updated successfully, but these errors were encountered: