-
Notifications
You must be signed in to change notification settings - Fork 597
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
Make dwv importable as an es6 module #399
Comments
As of today, es6 modules are only supported natively in Chrome (>=61), Opera (>=48) and Safari (>=10.1): see caniuse.com/#feat=es6-module. For the others:
|
Tried to require in Vue with
but getting
I'm using vue-cli's webpack template |
Curious what the priority is with this request, I have a react application that I would love to incorporate your viewer in to. Have you tried this already and run in to issues? If so what were the friction areas? Thinking of forking and trying to make it a react component but I’m curious what problems you’ve run into |
This issue is on hold, not because of frictions, but because I'm waiting for modules to be supported natively on Firefox so that I do not have to compile each time I want to try the code. Seeing that Mozilla is not moving too much on this, I'll maybe have to change my debug browser... |
Tried to require in Vue with
but failed to compile.
|
Ok, moving up the priority list! The plan is to use |
A good explanation page on contentful.com: es6-modules-support-lands-in-browsers-is-it-time-to-rethink-bundling (April 2017). |
@mingjuitsai, your problem is more related to #467. |
@mingjuitsai & @Doubledream, check out the new dwv-vue repo for an example integration with Vue.js |
Support update: now on all major browsers apart from IE! |
Note (to not forget): https://alexomara.com/blog/dual-packages-in-node-js-conditional-exports/ |
DWV must be importable as an es6 module
(different than current amd). This is needed for its integration in frameworks such as React or Angular2.Originates from #373, #367 and #363.
The text was updated successfully, but these errors were encountered: