Skip to content

Conversation

@EvanBacon
Copy link
Contributor

It's currently difficult to create more advanced aliases on top of react-native-web. We do the same in the expo-cli here. It'd be nice to emulate this without directly switching off of react-scripts. Here is an example that would work given this PR is merged: Code sandbox. You could then use Unimodules in code sandbox, or with react-scripts with minimal friction.

It's also bad practice to use react-native internals. The majority (if not all) of them don't work because the internal structure of react-native-web is optimized for babel-plugin-react-native-web.

CC: @necolas

@EvanBacon EvanBacon changed the title Prevent the use of react-native internals with react-native-web [Expo] Prevent the use of react-native internals with react-native-web Apr 16, 2019
@peterpme
Copy link

😍 any way I can do to push this along?!

@bugzpodder bugzpodder added this to the 3.x milestone Aug 11, 2019
@phibosGit
Copy link

How the impact on depends and legacy displays?

@EvanBacon EvanBacon closed this Aug 12, 2021
@EvanBacon EvanBacon deleted the @evanbacon/react-native-web-prevent-internals branch August 12, 2021 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants