You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Van-Nguyen could you do me a huge favor and look into this for me ASAP?
I've tried comparing the the output from webpack between cdn'd and non-cdn'd builds, but I don't know nearly enough about how this plugin & webpack work to be able to start figuring out whats going wrong.
To me it seems that maybe things are not being imported in time? I can confirm that in IE the libraries do make it there, but it could be that IE doesn't respect the order script tags are loaded when executing?
What's weird is that looking into it axios does seem to work properly, but it doesn't in my other project.
Meanwhile, prop-types give Failed prop type errors that don't appear if I don't cdn the package.
The text was updated successfully, but these errors were encountered:
For some reason, the CDN plugin is just not working in IE11 - every time it replaces a package that is used, an error of some kind happens.
The pages load fine in other browsers.
I've tried this all the way back to v2.
Heres an example repo.
@Van-Nguyen could you do me a huge favor and look into this for me ASAP?
I've tried comparing the the output from webpack between cdn'd and non-cdn'd builds, but I don't know nearly enough about how this plugin & webpack work to be able to start figuring out whats going wrong.
To me it seems that maybe things are not being imported in time? I can confirm that in IE the libraries do make it there, but it could be that IE doesn't respect the order script tags are loaded when executing?
What's weird is that looking into it
axios
does seem to work properly, but it doesn't in my other project.Meanwhile,
prop-types
giveFailed prop type
errors that don't appear if I don't cdn the package.The text was updated successfully, but these errors were encountered: