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
That is definitely a hazard with using amdefine/intercept -- it is a very global, coarse tool, that may not be appropriate for some dependencies. Local amdefine used in the modules that need it is the more robust route.
I can look at not doing the injection if import/export are present, but may just be moving the problem for you. If there is no define() injected, if you are using an AMD loader to load the code, then that will not work -- the module may get converted to ES5 format by babel, but since it will not be calling define(), seems like the module will not end up in the AMD loader registry?
Could you give some more detail on the use case, if not touching ES2015 import/export modules will help it?
When using with babel-register the
intercept
hook kills the registration for babel, so no babel compilation happens, resulting in errorThe text was updated successfully, but these errors were encountered: