@vitejs/plugin-react

The default Vite plugin for React projects.

• enable Fast Refresh in development (requires react >= 16.9)
• use the automatic JSX runtime
• use custom Babel plugins/presets
• small installation size

1// vite.config.js
2import { defineConfig } from 'vite'
3import react from '@vitejs/plugin-react'
4
5export default defineConfig({
6  plugins: [react()],
7})

Options

include/exclude

Includes .js, .jsx, .ts & .tsx by default. This option can be used to add fast refresh to .mdx files:

1import { defineConfig } from 'vite'
2import react from '@vitejs/plugin-react'
3import mdx from '@mdx-js/rollup'
4
5export default defineConfig({
6  plugins: [
7    { enforce: 'pre', ...mdx() },
8    react({ include: /\.(mdx|js|jsx|ts|tsx)$/ }),
9  ],
10})

node_modules are never processed by this plugin (but esbuild will)

jsxImportSource

Control where the JSX factory is imported from. Default to 'react'

1react({ jsxImportSource: '@emotion/react' })

jsxRuntime

By default, the plugin uses the automatic JSX runtime. However, if you encounter any issues, you may opt out using the jsxRuntime option.

1react({ jsxRuntime: 'classic' })

babel

The babel option lets you add plugins, presets, and other configuration to the Babel transformation performed on each included file.

1react({
2  babel: {
3    presets: [...],
4    // Your plugins run before any built-in transform (eg: Fast Refresh)
5    plugins: [...],
6    // Use .babelrc files
7    babelrc: true,
8    // Use babel.config.js files
9    configFile: true,
10  }
11})

Note: When not using plugins, only esbuild is used for production builds, resulting in faster builds.

Proposed syntax

If you are using ES syntax that are still in proposal status (e.g. class properties), you can selectively enable them with the babel.parserOpts.plugins option:

1react({
2  babel: {
3    parserOpts: {
4      plugins: ['decorators-legacy'],
5    },
6  },
7})

This option does not enable code transformation. That is handled by esbuild.

Note: TypeScript syntax is handled automatically.

Here's the complete list of Babel parser plugins.

reactRefreshHost

The reactRefreshHost option is only necessary in a module federation context. It enables HMR to work between a remote & host application. In your remote Vite config, you would add your host origin:

1react({ reactRefreshHost: 'http://localhost:3000' })

Under the hood, this simply updates the React Fash Refresh runtime URL from /@react-refresh to http://localhost:3000/@react-refresh to ensure there is only one Refresh runtime across the whole application. Note that if you define base option in the host application, you need to include it in the option, like: http://localhost:3000/{base}.

Middleware mode

In middleware mode, you should make sure your entry index.html file is transformed by Vite. Here's an example for an Express server:

1app.get('/', async (req, res, next) => {
2  try {
3    let html = fs.readFileSync(path.resolve(root, 'index.html'), 'utf-8')
4
5    // Transform HTML using Vite plugins.
6    html = await viteServer.transformIndexHtml(req.url, html)
7
8    res.send(html)
9  } catch (e) {
10    return next(e)
11  }
12})

Otherwise, you'll probably get this error:

Uncaught Error: @vitejs/plugin-react can't detect preamble. Something is wrong.

Consistent components exports

For React refresh to work correctly, your file should only export React components. You can find a good explanation in the Gatsby docs.

If an incompatible change in exports is found, the module will be invalidated and HMR will propagate. To make it easier to export simple constants alongside your component, the module is only invalidated when their value changes.

You can catch mistakes and get more detailed warning with this eslint rule.