he/him 
Fun fact: almost all of the problems related to using pixi.js, phaser.js, three.js (and by extension AR) with React Native are related to (the deeply integrated) Metro bundler 
and how it loads assets.
-
Metro and RN have tight integration for better and worse. For static assets, debugging modes, live/hot reload, stack trace click to source, even the refresh progress indicator.
I wouldn’t classify it as tight integration. There is a lot of custom endpoints and API, but nothing that prevents you from implementing it yourself outside of Metro? How do you propose they be decoupled and generic?
-
-
Would be sweet to see a stable spec for all those APIs. In the early days of RN, it was (is?) undocumented and frequently changing
-
Probably a bit too much trouble to keep the spec stable. Something I could see is a metro client package that implements whatever the spec is and can be updated whenever it changes. This package could be used by RN and other app frameworks.
- 8 more replies
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.