-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bundle and expose as ES module #221
Comments
I have used your same code of rollup as webpack didn't have very good support for exporting as ES. |
Maybe I should open a new issue for this, but it is really related to the present one: I'm not able to perform a very simple native ES6 import of the library: Do you plan to add ES6 support? FYI: it is not possible to do dynamic/conditional export in ES6; my own solution for such a cases was/is to publish 2 distros - one would looks like the one you already have and the second one for ES6 only - all IIF may be removed, all the functions would become top level in your module (they still be private and inaccessible for anyone else) and only export exposes the main function. WDYT? |
Have you tried importing from |
Works great, thanks! |
Just last suggestion - please consider to provide minified version of the |
Is your feature request related to a problem? Please describe.
I would like to use Polymer 3 with ApexCharts but Polymer 3 only works with ES Bundles. I would need Webpack bundling to get ApexCharts to work,.
Describe the solution you'd like
I would like to import this way :
import { ApexCharts } from 'apexcharts'
The text was updated successfully, but these errors were encountered: