Skip to main content

Expo

@rootnative/web-expo runs an Expo app on @rootnative/web in place of react-native-web. You keep your Expo setup: the dev server, expo export, and the Babel preset.

Install​

Install the package under the name react-native-web, with an npm alias:

npm install react-native-web@npm:@rootnative/web-expo

An Expo app with web support lists react-native-web already, and the alias takes its place. Restart the dev server with --clear after the change:

npx expo start --clear

Your code doesn't change, and TypeScript keeps the types of the react-native package.

The package depends on the same version of @rootnative/web, and works only with that version. If your app imports @rootnative/web itself, for example Head from @rootnative/web/dom, install the version that the package names.

How it works​

On the web, Expo's Babel preset rewrites import { View } from 'react-native' to an import of react-native-web/dist/exports/View. The package has a file at each of these paths, and each file loads only its own module of @rootnative/web. So the bundle has only the components that your app imports.

Expo also calls AppRegistry from react-native-web to start the app, and asks it for the reset styles of the page. The package gives both: your app renders with React DOM, and body gets no margin, as with react-native-web.

Expo's libraries import UIManager, NativeModules, LogBox, DeviceEventEmitter, NativeEventEmitter, and AssetRegistry on the web too. The package gives them as react-native-web does: NativeModules has no native module, LogBox does nothing, UIManager measures an element with the host methods of @rootnative/web, only JavaScript emits events on the two emitters, and AssetRegistry is the asset registry of @rootnative/web.

What works​

PartBehavior
Components and APIsEach one that @rootnative/web has. See Status.
Expo RouterTabs, a stack, links, the back button, and a URL that opens a screen directly.
The dev serverWorks.
expo export --platform webWorks with web.output: 'single', the default, and with 'static': Expo Router renders each route on the server, and the page hydrates.
Reanimated 4Animates the components. Expo's Babel preset runs the Worklets plugin, so the app needs no setup.
Image importsrequire('./logo.png') loads the image. On the web, Expo gives the import a uri, a width, and a height, and Image reads them.
react-native-svgRenders. The package has the assets registry that it loads on the web.

Names that aren't there yet​

A name of react-native that @rootnative/web doesn't have yet loads as a stub. The import works, so a library that imports the name and doesn't use it still loads. A use throws an error that names it, such as LayoutAnimation is not in @rootnative/web yet.

The largest ones today are LayoutAnimation, SectionList, VirtualizedList, ImageBackground, and SafeAreaView. The file node_modules/react-native-web/expo-exports.json lists all of them under missing.