John Lenz
John Lenz
I have two use cases for this: (1) conditionally use code if it is present. (2) make ES6 modules available to traditional scripts by delaying the loading of those script...
No, not polyfills, think a optional logging library or some such thing.
I should be specific about what my original motivation is here: I am trying to build a bridge between current module systems and ES6 modules. My goals were: - allow...
Right, there I have to (a) a new API to use the legacyRegistry (b) create a means of resolving the relative paths used in the script. I want to avoid...
Is there any update on this? I'm still haven't seen any proposal to solve circular imports in a meaningful way. "import(...).then(...)" has the wrong timing.
https://developer.mozilla.org/en-US/docs/Web/API/Window/unload_event
I think the test framework can be migrated to use Promise rather than goog.Promise. The polyfill should work.
I think we are talking past each other. The test framework itself should be as independent of the test running as we can make it. It should use the native...
Many things break if goog.global isn't set correctly. Having it use global in node would be the correct thing. That should be fixed. On Mon, Jun 4, 2018, 3:15 PM...