SebastianVerified account

Is there any specific that you think couples React Native and Metro?

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.

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.