vite-plugin-react-swc

• Support Vitest deps.experimentalOptimizer (#115)

• Add type: module to package.json (#101). Because the library already publish .cjs & .mjs files, the only change is for typing when using the node16 module resolution (fixes #95)
• Throw an error when the MDX plugin is after this one (#100). This is an expected breaking change added in 3.2.0 and this should people that were using both plugins before this version to migrate.

• Support Emotion via the new jsxImportSource option (fixes #25)

To use it with Emotion, update your config to:

export default defineConfig({
  plugins: [react({ jsxImportSource: "@emotion/react" })],
});

• Fix HMR when using Vite base option (fixes #18)
• Fix usage with workers (fixes #23)
• Fix usage with Vite Ruby and Laravel Vite (#20)
• Fix plugin default export when using commonjs (fixes #14)

This is plugin is now stable! 🎉

To migrate from vite-plugin-swc-react-refresh, see the 3.0.0-beta.0 changelog.

• breaking: update plugin name to vite:react-swc to match official plugins naming
• fix: don't add React Refresh wrapper for SSR transform (fixes #11)

Fix package.json exports fields

This is the first beta version of the official plugin for using SWC with React in Vite!

Some breaking changes have been made to make the plugin closer to the Babel one while keeping the smallest API surface possible to reduce bugs, encourage future-proof compilation output and allow easier opt-in into future perf improvements (caching, move to other native toolchain, ...):

• Automatically enable automatic JSX runtime. "classic" runtime is not supported
• Skip transformation for .js files
• Enforce useDefineForClassFields
• Don't pass esbuild.define config option to SWC. You can use the top level define option instead
• Use default export

To migrate, change your config to:

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react-swc";

export default defineConfig({
  plugins: [react()],
});

This new release also include a runtime check for React refresh boundaries. When the conditions are not met (most of the time, exporting React components alongside functions or constant), the module is invalidated with a warning message to help you catch issues while keeping you page up-to date with code changes.

Add LICENSE

Initial release