Open mnlbox opened 4 years ago
I don't want to include code splitting in the main branch due to the issues that exist around with code splitting and bundling 3rd party dependencies. If I can sort this out, I'd consider it :).
Also, I don't believe you can have cjs
and esm
code split outputs in the same directory. This increases the length of our imports which I'd rather avoid.
I think it's a good idea to enable
code splitting
andesm
export together in the main branch. Then we can haveesm
and also splitcjs
version together. And use our component in both ways like this fores
import:and like this, if we have default export:
or like this, of we have named export:
@HarveyD What's your idea?