Quick example of a corner cases that you can't use the loader api to implement @wycats @domenic @BrendanEich https://gist.github.com/calvinmetcalf/a3ea472be21c21169310 …
-
-
@wycats@domenic@BrendanEich yes bit you can't statically analyze the deps but defer evaluation until the function is called -
@CWMma@domenic@BrendanEich Why do you have to do that? -
@wycats@domenic@BrendanEich to load the script statically and take advantage of loader hooks -
@wycats@domenic@BrendanEich there is an issue https://github.com/calvinmetcalf/es6-translate/issues/13 … but the loader hooks don't cover this case well -
@CWMma@domenic@BrendanEich You would implement a `require` that synchronously executed the module and registered it. -
@wycats@domenic@BrendanEich but you need to load it first, what you suggested works for dealing with cjs circular references -
@CWMma@domenic@BrendanEich I think you're assuming that you have to do all the work in terms of the loader hooks. require() is just a lib -
@wycats@domenic@BrendanEich it dies if you need to execute CJS code from within ES6 code. - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.