We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Related: ant-design/ant-design#11263 babel/babel#2212
Should stop using babel-plugin-add-module-exports Should stop transpiling to wrong module syntax
Should use babel-plugin-add-module-exports@next and turn on addDefaultProperty option.
The text was updated successfully, but these errors were encountered:
We've tried to remove babel-plugin-add-module-exports, unfortunately, it's a breaking change.
babel-plugin-add-module-exports
Sorry, something went wrong.
I think you can make it backward compatible by make module and module.default both refers to the same thing.
babel-plugin-add-module-exports@0.3 (not published currently) has this option:
addDefaultProperty This will cause a second line of code to be added which aliases the default name to the exported object like so:
module.exports = exports['default']; module.exports.default = exports['default']
Any movement with this? @yesmeck
No branches or pull requests
Related:
ant-design/ant-design#11263
babel/babel#2212
Should stop using babel-plugin-add-module-exports
Should stop transpiling to wrong module syntax
Should use babel-plugin-add-module-exports@next and turn on addDefaultProperty option.
The text was updated successfully, but these errors were encountered: