beknar.askarov

Maybe obvious, but there are two approaches at least developers themselves can manage; replace imports of `react` with `haunted` Buildtime using bundler to replace and runtime using "importmap" example of...

plunkr looks broken, at least for me. here is the page itself https://run.plnkr.co/plunks/8lukaUKTSzv6HOn5/, but you will have to check for sources in inspector

@justinfagnani importmap does not require tools as you can see in plunkr example above. But I see your point. **Factory** vs **Dependency Injection**. Will be be nice to start with...

Thank you No it is not blocking, just something I was curious about. I thought that I have missed on some news or insight in browser render optimisation:) On Sat,...

Thats maybe because browser vendors moved input updates into render cycle after raf. Polymer uses microtaks for batching prop updates. There is no mechanism to synchronise components. Eventloop runs microtasks...

One thing to note. Users should use promise from webcomponents polyfill and do not load their own. Since webcomponents polyfill adds mutation observer for older browsers instead of default behaviour...

In my opinion Consumer component always has to render into light DOM. Just like react behaves. I left it that way because there was no option to render to light...

So in other words, your implantation has to replace current one On Thu, 14 Mar 2019, 19:34 Beknar Askarov, wrote: > In my opinion Consumer component always has to render...

Consumer and Provider have to be virtual components, but since there is now teardown functioning properly and other bugs with virtual components they are components right now On Thu, 14...