Jarda Kotěšovec

@trevoreyre I believe for this use case composition api will come to rescue :-). Have you considered to ship autocomplete component with composition api? I think it would be great...

@jsumners There is kind of automatic PR already - https://github.com/pinojs/pino-debug/pull/60 . Any idea why the tests are failing there, has something significantly changed in pino 7?

@toxicFork Ok, thanks. Current work around with webpack currently looks like: ``` require('imports?THREE=three!three/examples/js/renderers/Projector'); require('imports?THREE=three!three/examples/js/renderers/CanvasRenderer'); ```

This sounds like this chrome issue: mrdoob/three.js#8666 But also getting ton of these messages in chrome and firefox ``` debugId may not be empty ```

I also have not seen this issue with latest versions, including dev build.

@toxicFork Good news on fiber implementation, but may I ask, whats the motivation for using typescript for new implementation? I suspect that code base ends up less approachable for contributors...

@toxicFork On different note. Do you think that it would be feasible to make new implementation somewhat modular, similarly as current Three.js? It would be awesome if would be possible...

@toxicFork And is not [flow](https://flow.org/) more suitable since react use that? There is [discussion](https://github.com/facebook/react/issues/9103) about exposing react reconciler and there is definitely intention to include flow types for that api....

@toxicFork Hey, just wondering, do you have any update on react-three-rendered-fiber progress? The repo seems quiet lately :-).

@lukaszmakuch I am not involved in this particular project, but definitely would appreciate such flexibility for 'multiple sessions' setup.. @dougwilson What you think? Would you be willing to accept such...