React Native Web addon for Storybook

This addon configures @storybook/react to display React Native (RN) projects using React Native for Web (RNW)

• React Native Web addon for Storybook
  • Getting Started
  • Common issues
  • Config options
    • Untranspiled react native libraries
    • Aliasing react native web libraries
    • Adding babel plugins
  • Configuring popular libraries
  • Adding support for static assets and svgs
  • Node polyfills for webpack 5
  • Known limitations

See the FAQ for common questions.

You can read more about this package in this blog post.

To contribute see the contributing guide here

Heres a screen shot of how you could use this alongside storybook/react-native, the image is taken from the following starter code

Getting Started

Assuming you've got an existing RN project, run the following from the project root:

1npx sb init --type react
2yarn add react-dom react-native-web babel-plugin-react-native-web @storybook/addon-react-native-web @react-native/babel-preset --dev

Then edit your .storybook/main.js:

1module.exports = {
2  addons: [/*existing addons,*/ '@storybook/addon-react-native-web'],
3};

From here, you should be able to write stories incorporating your RN components according to the Storybook for React instructions.

Common issues

Please see the FAQ for common issues like the "loader not found" error.

Config options

Most packages should work without extra changes however in some cases extra steps are needed. One common example is "reanimated" which requires some babel config and extra transpilation.

Untranspiled react native libraries

Many react-native packages are shipped untranspiled and this doesn't work for the web platform. If you receive errors like "proper loader not found" after adding a package try adding it to the modulesToTranspile option for this addon.

You can do that like this:

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        modulesToTranspile: ['react-native-package-name'],
8      },
9    },
10  ],
11};

Aliasing react native web libraries

Some react-native packages recommend module aliasing as a means of importing and using the web variant of an existing package. If you need to add additional key:value pairs to webpack's config.resolve.alias, use the modulesToAlias option for this addon. You don't need to add react-native-web to this list as it is already included by default.

You can do that like this:

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        modulesToAlias: {
8          'react-native-package-name': 'react-native-web-package-name',
9        },
10      },
11    },
12  ],
13};

Replace react-native-package-name with the name of a real package.

Adding babel plugins

It's common to provide a babel plugin for certain packages in the react native eco system and you can pass a list of these to the addon.

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        babelPlugins: ['babel-plugin-name'],
8      },
9    },
10  ],
11};

Configuring popular libraries

Many libraries work without extra config, heres some examples of config required for some packages.

Note: react-native-vector-icons requires some extra steps due to fonts required and there will be a future addon with that config included.

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        modulesToTranspile: ['react-native-reanimated'],
8        babelPlugins: [
9          '@babel/plugin-proposal-export-namespace-from',
10          'react-native-reanimated/plugin',
11        ],
12      },
13    },
14  ],
15};

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        modulesToTranspile: ['react-native-vector-icons'],
8      },
9    },
10  ],
11};

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        modulesToTranspile: ['react-native-vector-icons'],
8      },
9    },
10  ],
11};

1module.exports = {
2  addons: [
3    /*existing addons,*/
4    {
5      name: '@storybook/addon-react-native-web',
6      options: {
7        modulesToTranspile: [
8          'react-native-reanimated',
9          'nativewind',
10          'react-native-css-interop',
11        ],
12        babelPresets: ['nativewind/babel'],
13        babelPresetReactOptions: { jsxImportSource: 'nativewind' },
14        babelPlugins: [
15          'react-native-reanimated/plugin',
16           [
17            '@babel/plugin-transform-react-jsx',
18            {
19              runtime: 'automatic',
20              importSource: 'nativewind',
21            },
22          ],
23         ],
24      },
25    },
26  ],
27};

Adding support for static assets and svgs

Install @svgr/webpack and url-loader

1module.exports = {
2  /*existing config*/
3  // to provide a public export for assets
4  staticDirs: ['<path_to_assets>'],
5  webpackFinal: async (config) => {
6    const fileLoaderRule = config.module.rules.find(
7      (rule) => rule.test && rule.test.test('.svg'),
8    );
9
10    if (fileLoaderRule) {
11      fileLoaderRule.exclude = /\.svg$/;
12    }
13
14    config.module.rules.push({
15      test: /\.svg$/,
16      use: ['@svgr/webpack', 'url-loader'],
17    });
18
19    return config;
20  },
21};

Node polyfills for webpack 5

install node-polyfill-webpack-plugin

1const NodePolyfillPlugin = require('node-polyfill-webpack-plugin');
2
3module.exports = {
4  /*existing config*/
5  core: {
6    builder: 'webpack5',
7  },
8  webpackFinal: async (config) => {
9    config.plugins.push(new NodePolyfillPlugin());
10
11    return config;
12  },
13};

Known limitations

• Libraries that don't support react-native-web will not work
• Components will display on the web so may not be the same as a component on a mobile device since dom versions of those components may be used (like <div> and span)
  • when using primitives such as View/Text or other cross platform components then the difference should be minimal.