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.
-
A package for the client would be a great first step and would probably be very useful with RN-Web. But the lack of a stable spec hurts anyone on RN who doesn’t use Metro.. haul has to scramble to meet that moving target
Scramble? I understand it’s annoying but nobody has been working full time on Metro in months, and for the most part it’s API has been stable too. I don’t feel like the actual difficulty is being accurately presented here.
-
-
I think they need to change how polyfills n such work across different rn versions. 59 & 60 had a bunch of changes. Also since the inspector is pretty tied to Metro they have to update that as well. It’d be nice if RN used a bundler that someone was actively working on.
-
@motiz88,@rickhanlonii,@dan_abramov and I have all been working on Metro quite a bit in the past months. - 4 more replies
New conversation -
-
-
I’m sure you’re right that it has calmed down. For a while there, haul was breaking with every release of RN. Not that I’m a webpack advocate! But I do admire how people can use one packager for RN+Browser+SSR
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.