react-strict-dom icon indicating copy to clipboard operation
react-strict-dom copied to clipboard

Published 20 hours ago • verified publisher icon facebook

Eject expo example

Open necolas opened this issue 7 months ago • 6 comments

Describe the feature request

Expo has a number of issues and it is preventing us from testing as accurately as I'd like. Fixing these issues is not a priority for Expo. We should look into ejecting, forking, patching, de-frameworking, or other ways to work around these problems preventing Expo from working with xplat React.

  1. ~Issues upgrading. Each time I try to upgrade the SDK there are new issues. Most recently I can't upgrade to Expo 51 because Expo packages are now missing dependencies and haven't been tested to work in npm monorepos~
  2. Can't use latest React Native. We're stuck using whatever version of RN the SDK requires, but we're increasingly relying on features in latest releases or nighties.
  3. Installs unnecessary dependencies. We don't need RNfWeb but Expo forces this for Web.
  4. Metro and Expo will lack StyleX integration on Web. I don't think we have a way to get the output from the StyleX CLI back into Expo.
  5. Expo controls the outer document and RN container, which limits our ability to prototype cross platform <body> etc components.

necolas avatar Jul 01 '24 16:07 necolas