Description
Hey everyone! I am having the following issue, if I export like this:
import GoogleMap from './google_map';
export default GoogleMap;It will build:
module.exports = GoogleMap;However, when including named exports:
import GoogleMap from './google_map';
export { namedExport1, namedExport2 } from './named_exports;
export default GoogleMap;it changes to:
exports.namedExport1 = namedExport1;
exports.namedExport2 = namedExport2;
...
exports.default = GoogleMap;Which results in the following error:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
I am pretty sure you will ask why we do need default exports, in my case I've a library that is used by a lot of people, I switched to microbundle a bit ago and realized later on this was buggy and it won't work with SSR unless we do module.exports, thing is even if I want to change the way we import / export to work with microbundle, I need to provide backwards compatibility or something...
I think this might be related to #264 and #306 but I am not completely sure if that's the case.