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.
-
-
-
Replying to @cpojer
Asset loading doesn't work with the three libraries I just listed, Dev tools (error messages, source maps) are still pretty not great, the whole thing is too deeply coupled with the rest of React Native. It'd be nice if people could use parcel, roll-up, webpack, etc...
3 replies 1 retweet 9 likes -
Replying to @Baconbrix @cpojer
Is there any specific that you think couples React Native and Metro?
2 replies 0 retweets 2 likes -
Dev tools. There also appear to be hard coded metro values in RN. I would love to see a more agnostic system.
2 replies 0 retweets 2 likes -
Replying to @Baconbrix @cpojer
I'm mostly asking because I am writing a bundler for RN and haven't encountered any issues. Mirroring the Metro HTTP server endpoints are annoying, but I don't know of any agnostic way you could do it?
1 reply 0 retweets 1 like -
MBP keyboard got me off code for the next 40 hours :/ if I see anything more specific than the problems I outlined, I'll let you know. Why a new bundler and not just added compatibility for all the existing options (asking cuz I'm working on RNWeb and other platform parity)
1 reply 0 retweets 2 likes
Sweet! Thank you! There's lots of reasons. There's two discussions here though. The relevancy of Metro, and replacing/improving it. And it's association with React Native. As for "why a new thing", my tweets about Rome are relevant here.
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.
he/him 