Neehar Venugopal

Not a specific subset per se, but only pull in what is required. I think there is a difference between transpilation and bundling wrt what we enforce on end users,...

@elgerlambert any examples of how one can do this?

Hey folks, this is turning into a blocker for us as well. > Can you do following instead? > > 1. Have initialActions in the modules added via DynamicModuleLoader >...

@NekR well, my personal use case stems from developit/preact-compat#262. Since React allows iterable structures as children, it would be reasonable to assume that other developers coming to Preact would also...

@NekR @developit So if I understand correctly, there are 3 choices in front of us 1. Polyfill `for...of` and `Symbol`, and go with the approach in this PR - Pros...

@NekR unfortunately even if we write our own code to consume the iterator, the iterator *protocol* is well defined and implemented across the board. And that protocol does not define...

@developit @robertknight That seems like a reasonable solution. The only caveat I have is that if we do something along the lines of detecting if `Array.prototype.from` exists, and only then...

>Hmm. If you are using Preact in order to reduce the script size of your application, are you likely to >be using a library like Immutable which is much larger...

> Using Babel's transpilation of for ... of to handle the iteration protocol: This is exactly what I have done in this PR 😄 @robertknight >In addition, since true iterables...

> If the child passed in is an iterable presumably that means that Symbol.iterator must already have been defined or polyfilled in order to implement the interface. So Preact can...