How to Use React Native Libraries in Your Vega App

Vega Open Beta Knowledge Base
1

Vega uses a fork of React Native (React Native for Vega), so not all RN libraries work out of the box. That means if you are porting your app to Vega, you may need to wire in a Vega fork of some of your libraries as well.

The good news is that we have ported many of the most popular libraries used in TV apps, and we’ve also built the Vega Module Resolver Preset (VMRP), which replaces third-party libraries with their Vega-platform ported equivalencies.

Let’s break it down with the four categories of libraries for Vega:

1. Libraries with Vega forks
2. Libraries that depend on another forked library
3. Libraries that work out of the box
4. Libraries that don’t work with Vega yet

1. Libraries with Vega forks

Libraries with Vega forks work natively in your Vega app. You can find a list of them in the documentation. They are supported as part of the @amazon-devices/ namespace.

There are two ways to use a forked library:

1. Import the fork directly by its @amazon-devices/ name. Install the fork:

npm install @amazon-devices/react-native-gesture-handler@2.0.1759135970

Then import it using the @amazon-devices/ prefix:

import { ... } from '@amazon-devices/react-native-gesture-handler'

This works for your own code, but it won’t help with transitive imports. If another library in your dependency tree imports react-native-gesture-handler by its original name, that import won’t be redirected and will break at runtime. For that reason, option 2 below is recommended for most apps.

2. Keep your original import names by using the VMRP, which swaps the original library for the fork at bundle time. See How to use the Vega Module Resolver Preset (VMRP) for the setup steps and an explanation of how it works.

The VMRP keeps your import statements platform-neutral and handles transitive dependencies inside other libraries automatically, so we recommend using it in most Vega apps.

Check the Supported Libraries and Services documentation for more information and a complete list of the natively forked libraries.

2. Libraries that depend on another forked library

A lot of libraries rely on other libraries to work. For example, react-native-chart-kit relies on react-native-svg to work.

These libraries won’t work on Vega on their own, they have internal imports of the original package that need to be redirected to the Vega fork via VMRP.

Simply adding @amazon-devices/react-native-svg to your package.json does not redirect that internal import because Metro still tries to resolve the string react-native-svg, and the build breaks. You’ll need to use the VMRP (see How to use the Vega Module Resolver Preset (VMRP)), because it rewrites imports inside libraries you can’t modify.

Install the parent library, and then install both the fork and its upstream at their exact pinned versions:

npm install react-native-chart-kit@7.0.1
npm install --save-exact react-native-svg@13.14.0
npm install @amazon-devices/react-native-svg@2.0.1759135970

Your dependencies will then look like:

 "dependencies": {
     ...
     "@amazon-devices/react-native-svg": "2.0.1759135970",
     "react-native-svg": "13.14.0",
     "react-native-chart-kit": "~7.0.1",
     ...
}

You’ll need to include both the @amazon-devices/ version and the upstream version of the dependency. The fork provides the native implementation, and the plain package must be present at the exact version the fork aliases so the VMRP can map it. (Only the aliased library needs an exact pin, the parent library can use a normal version range.)

3. Libraries that work out of the box

The simplest libraries are the ones that already work with Vega, no porting required. These are pure JavaScript libraries with no native module code. They don’t touch any platform-native layer, so they run on React Native for Vega the same way they run on standard React Native. Just import them like you normally would.

4. Libraries that don’t work with Vega yet

Finally, there are the libraries that aren’t available on Vega yet.

Tell us which ones you would like to see come to Vega!

We’re working on making Vega better every day, and that includes porting the libraries you’d like to see.

Last updated: July 20, 2026